Traders

Cancel a trader export job

Cancels a submitted export and returns the job resource, the same shape the status route returns. A queued job reads cancelled at once and no worker will start it. A running job reads cancel_requested until the worker reaches its next safe point, then cancelled: the worker checks every 5 seconds while it reads the snapshot and between upload parts, and once more at the last point before the file is published; a storage request already in flight finishes first (each is bounded at 120 seconds), and a partial upload is discarded. If the worker itself stops first, the job reads cancelled after its 30-minute lease lapses, at the next hourly cleanup. A job a cancel can no longer reach is returned unchanged with 200: once its upload is being completed it finishes as ready (or reconcile_required, then ready or failed), and ready, failed, expired and cancelled jobs are terminal. A cancel never deletes a ready file; compare status before and after. Repeating the request is safe: it converges on the same state and never repeats a transition, so a client that lost the answer can send it again or read the status route. While terminal is false, poll the status route after poll_after_s. Quota is unchanged: the submit's reservation keeps counting toward the per-user daily and per-address hourly export caps for its full window, as a failed export's does, and a job its owner asked to cancel is never reused by a later submit, which reserves a new job. Webhook endpoints subscribed to export_job_cancelled receive it when the job reaches cancelled. An unknown job id, or a job owned by another account or submitted for another trader, answers 404 exactly as the status route does.

post/api/v1/trader/{address}/export/cancel

Path parameters

addressstring required

Trader wallet address (0x...), known trader username-style lookup, or trd_-prefixed trader ID emitted by this API.

Query parameters

job_idinteger required

Export job id returned by the submit route.

Headers

X-Query-Validation'strict'

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Response

The job after the cancel: cancelled, cancel_requested, or unchanged when a cancel can no longer reach it.

object'trader_export_job' required

Changes

Changed in 2 of the 89 revisions of this API.1011

Sep 23, 2026ece7a25b7a441010See the full diff
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new freshness_ceiling_unsatisfied enum value to the / response property for the response status
  response-property-enum-value-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
Sep 23, 2026c6a3d3420dc51See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history