Skip to main content
Deleting a project or sheet removes it: it is no longer returned by or accessible through the API.

Endpoints

Delete Project · Bulk Delete Projects · Delete Sheet · Bulk Delete Sheets

Deleting one resource

A DELETE returns 204 No Content on success:
An ID that does not exist or is not accessible with your key returns 404 Not Found:
Deleting the same ID again also returns 404, so retries are safe.

When deletes are disabled

Deletes can be turned off for an API key. Every delete endpoint, single and bulk, then returns 403 Forbidden with error.code ACCESS_DENIED, and nothing is deleted. Retrying will not help; contact Atlas Tube if your key needs to delete.

Deleting in bulk

Send up to 100 IDs in one call. Each ID is handled on its own; the call is not all-or-nothing.
The project route is the same, with a projectIds array. The response lists one result per ID, in request order. When every ID is deleted you get 200 OK. When at least one fails you get 207 Multi-Status; the others are still deleted:
Check each item’s status rather than relying on the HTTP status alone. Treat an unrecognised code as retryable.

Request validation

The request is rejected with 422 Unprocessable Entity, before anything is deleted, when the ID array is missing, empty, contains a non-UUID or a duplicate, or has more than 100 IDs. The list is never silently truncated. IDs are compared case-insensitively, so two spellings of the same UUID count as duplicates:

Notes

  • Deleting a project deletes its sheets. You do not need to delete them separately. Its sheets stop appearing and requests for them return 404.
  • Repeating a delete is safe. A repeated single delete returns 404; in a bulk call an already-deleted ID comes back as NOT_FOUND.