Skip to content
API console (try a request with your own key)Get early access

Deleting a job

Sent the wrong file, or one that should never have left your network? Delete its job, and everything of it goes:

Terminal window
JOB_ID=7c9e6679-7425-40de-944b-e07fc1f90ae7 # the jobId the submission answered with
curl -sS -X DELETE "https://api.speccapture.com/v1/extractions/$JOB_ID" \
-H "Authorization: Bearer $SPECCAPTURE_API_KEY"

Paste into a terminal with SPECCAPTURE_API_KEY set. Needs curl; scripts also use bash and jq.

DELETE /v1/extractions/{jobId} answers 204 with no body, and from that moment the job is gone: every request about it - the job, its sheets, its export - answers 404 not_found, its view links show only that the link has expired or was withdrawn, and a webhook event about it that has not been sent yet is never sent. The uploaded file, the page images, every sheet’s values, notes and tables, and the stored exports are erased within minutes. It cannot be undone.

  • Credits: a job that has finished keeps what it spent: the sheets were read. A job still queued, splitting or extracting stops, and every credit it has not spent comes back to the workspace at once, a sheet being read at that moment included - its values are never delivered.
  • Who may delete: a live key acting as the workspace’s owner or an admin, as for view links and webhooks. A test key is refused with 403 live_key_required, a key acting as a member with 403 role_not_allowed. In the dashboard, the owner and admins have Delete on the document’s page and in each document’s menu.
  • Refusals: another workspace’s job, an id nobody issued, or a job already deleted all answer 404 not_found, so deleting twice is harmless.
  • Your copies: exports you have downloaded and values your own software stored are yours, and are not touched.