Skip to main content
DELETE
Delete job
Permanently deletes a job posting, and every contact and conversation attached to it. This action cannot be undone.

Overview

This endpoint removes a job posting from your account. It is the widest-reaching delete in the public API: the cascade takes the job’s contacts and their conversations with it, not just the links between them.

Use Cases

  • Remove Obsolete Jobs: Clean up jobs that are no longer relevant
  • Archive Old Postings: Permanently remove outdated job postings
  • Compliance: Delete jobs for data retention compliance
  • Organization: Maintain a clean job library

Permanent Deletion Behavior

Deletion is irreversible, and it removes the job’s language requirements and job links along with the posting itself.

Impact on Existing Data

The cascade deletes contacts and conversations. Every contact whose job this is goes, and so does every conversation of theirs — transcripts, recordings and analyses included. A contact assigned to this job and others is deleted too: the cascade is by job, not by “contacts left with no job”. None of it is readable through the API afterwards.If you only want to stop using a job, set its status to CLOSED instead — that changes nothing else. Delete it only when you intend to lose the data attached to it.

Company Isolation

You can only delete jobs that belong to your API key’s company. A job from another company answers 404 Not Found — the same status and the same body as an id that exists nowhere, so the response never confirms that an id exists somewhere else.

Error Scenarios

  • 404 Not Found: No job with that id is available to your API key. It does not exist, it has already been deleted, or it belongs to another company — the three are deliberately indistinguishable, so do not branch on this status to detect a permission problem.
This route does not treat a delete of an unknown id as a no-op success. It used to answer 200 with "data": false for an id that never existed; it now answers 404, matching DELETE /agents/{id}. A 200 means a job was really deleted.

Jobs Resource Guide

Learn about job management

List Jobs

View all active jobs

Create Job

Create new job postings

Authorizations

Authorization
string
header
required

API key for authentication using Bearer scheme

Path Parameters

id
string<uuid>
required

Query Parameters

companyId
string

Required for ATS API keys to specify which company to access. Ignored for standard company API keys.

Response

Deleted successfully

id
string<uuid>
required

Id of the deleted resource

deleted
enum<boolean>
required

Always true; a failed delete answers with an error status

Available options:
true
Example:

true