Extractions
Cancel a Twitter extraction job with the Xquik API
Cancel an active Xquik extraction job by its ID. The job stops, saves no rows & uses no credits. Handle the 200, 401, 403, 404, 409 & 429 API responses.
- 200
- 401
- 403
- 404
- 409
- 429
DELETE
Cancel a Twitter extraction job with the Xquik API
Cancel one extraction job
SendDELETE /extractions/{id} to stop a pending or running job. The job
ends as canceled. It saves no rows & uses no credits. A repeat request on a
canceled job answers 200, so a retry is safe.
Use the job ID from Create Extraction or
List Extractions. An
API key needs the exports scope for this route.
Know when a job can stop
Only apending or running job can stop. A finished job answers 409 with
its status. Its rows stay as they were.
To keep the rows a job already found, let it finish. Then read them through
Extraction results.
Headers
string
An OAuth bearer token formatted as
Bearer YOUR_TOKEN. Send this header or x-api-key, not both.Path parameters
string
required
Extraction job ID returned from Create Extraction or List Extractions.
Response
- 200 Canceled
- 401 Unauthenticated
- 403 Forbidden
- 404 Not found
- 409 Already ended
- 429 Rate limited
Related. Create Extraction starts a new job, and List Extractions shows each job’s status.