Delete a job and its associated data
The Delete Job endpoint removes a job and its associated data from the system. This is useful for cleaning up completed jobs or cancelling jobs that are no longer needed.
Deleting a job will permanently remove all associated data including results. This action cannot be undone.
The unique identifier of the job to delete
API key for authentication (optional for some endpoints)
Confirmation message that the job was deleted
Completed Jobs
Delete jobs after you’ve retrieved and stored the results elsewhere. This helps keep your job list clean and reduces storage costs.
Failed Jobs
Delete failed jobs that you don’t plan to retry. You can review the error details before deletion if needed.
Test Jobs
Clean up jobs created during testing or development to avoid clutter in production environments.
Cancelled Processing
If you need to stop a job that’s taking too long or is no longer needed, delete it to free up resources.
Here’s an example of cleaning up old completed jobs:
Check Status First: Before deleting, check the job status to ensure you don’t accidentally delete a job that’s still processing.
Save Results: Always retrieve and save important results before deleting completed jobs.
Regular Cleanup: Implement regular cleanup routines to manage storage costs and keep your job list manageable.
Permanent Action: Job deletion is permanent and cannot be undone. Make sure you have saved any important results.
Job Not Found (404)
The job ID doesn’t exist or has already been deleted. This is also returned if the job was automatically cleaned up.
Permission Denied
You don’t have permission to delete this job. Jobs can only be deleted by the user who created them.
System Error
An internal error occurred while trying to delete the job. You can retry the request.
Deletion operations are generally not rate-limited as strictly as other operations, but excessive deletion requests may be throttled.