applications.delete

Delete an application

Request: DELETE/api/v1/applications/{applicationId}
Scope required: applications:write
Effect: Deletes something. Confirm with a person before calling it.
Acts on: Acts on the account’s own job search.
MCP tool: applications_delete
Environment: Live and sandbox alike.
Request body: JSON.

What it does

Removes a card from its board together with its status history, its interviews and its coach notes. This cannot be undone, and there is no archive to recover it from — `applications.move` to `archived` is what an agent should reach for when the intent is "stop showing me this". The company and the résumé the card referred to are left alone. Answers 204 with no body. Send the `ETag` from `applications.get` as `If-Match` to be refused with 412 if the card changed since you read it.

Parameters

Parameters this endpoint accepts, where each one goes, and whether it is required
Name	Sent in	Requirement	Accepts
applicationId	path	Required	string
If-Match	header	Optional	string — The ETag of the version you read. The write is refused with 412 if the resource has changed since.

Response

Answers 204 with no body.

Examples

Delete a card filed by mistake

Delete a card filed by mistake — request

curl -s -X DELETE https://www.jobapplicationtracking.com/api/v1/applications/app_123 \
  -H "Authorization: Bearer $JAT_KEY"

Delete a card filed by mistake — response

null