Skip to main content
DELETE
Cancel an active request before it’s completed. This is useful when a request is no longer needed or when you want to modify the request parameters. Only pending requests can be cancelled.
Cancelled requests cannot be restored. If you need the same request processed, you’ll need to create a new one.

Authentication

Authorization
string
required
Your API key for authentication

Path Parameters

id
string
required
The unique identifier of the request to cancel

Response

error
boolean
Whether an error occurred
msg
string
Success message confirming cancellation
data
object

Cancellation Rules

What Can Be Cancelled

Pending Requests

Status: pending
  • Waiting for reviewer response
  • Can be cancelled without impact

What Cannot Be Cancelled

Completed Requests

Status: completed
  • Reviewer has submitted response
  • Use feedback system instead
  • Response data is final

Final Status Requests

Status: timeout, cancelled
  • Already in final state
  • No further action possible
  • Historical record preserved

Impact of Cancellation

On API Usage

Refund Policy: Usually refunded to API quota
  • Request never reached a reviewer
  • No processing time invested
  • Full refund to your hourly limit
Example: If you’ve used 45/100 API calls this hour and cancel a pending request, you’ll have 46/100 remaining.

On Reviewers

Cancelling pending requests has minimal impact on reviewers:
  • Request is removed from their queue
  • No wasted reviewer effort
  • Keeps the review queue clean
  • Cancel requests as soon as you know they’re not needed
  • Review request parameters carefully before creating
  • Avoid frequent cancellations to maintain workflow efficiency

Cancellation Strategies

Batch Cancellation

Cancel multiple requests efficiently:

Smart Cancellation Logic

Implement intelligent cancellation based on request status:

Error Handling

Common Error Scenarios

Causes:
  • Invalid request ID
  • Request doesn’t exist
  • Request doesn’t belong to your API key
Cause: Request is already completed, timed out, or cancelled. Solution: Use the feedback endpoint for completed requests instead.
Cause: Request was created by a different API key. Solution: Ensure you’re using the correct API key that created the request.

Error Recovery

Handle cancellation errors gracefully:

Alternative Actions

Instead of Cancelling

Consider these alternatives:
Consider waiting for completion and then providing feedback on the response quality.
Create a new request with improved parameters rather than cancelling and losing the original request history.
Some use cases: Add additional context to help reviewers rather than cancelling. (Note: This feature may be added in the future)
Future feature: Adjust request priority instead of cancelling. (This feature may be added in the future)

Best Practices

When to Cancel

  1. Early Cancellation: Cancel as soon as you know the request is no longer needed
  2. Batch Processing: If cancelling multiple requests, use batch operations
  3. Communication: Provide cancellation reasons when possible (future feature)
  4. Timing: Avoid cancelling requests that are likely to be completed soon

When Not to Cancel

  1. High Priority: Don’t cancel urgent requests without good reason
  2. Near Completion: If a request is likely to complete soon, wait instead
  3. Frequent Pattern: Avoid creating a pattern of frequent cancellations

Next Steps

Create New Request

Create a new request to replace the cancelled one with improved parameters.

Request Feedback

Learn how to provide feedback on completed requests instead of cancelling.

Monitor Requests

Track your request patterns to optimize future request parameters.