Skip to main content
The generic document endpoints for a teardown your org owns. For slot-specific documents (harvest list / OCCM / aircraft-details / non-incident-statement), see the slot endpoints.

Upload

Attach a document to one of your teardowns. The URL is also appended to the teardown’s documents[] array so it shows up in detail responses.

Headers

string
required
Bearer tdao_live_…
string
required
string
required
multipart/form-data (curl’s -F does this automatically).

Form fields

file
required
The file to upload.
string (CSV)
Optional. Comma-separated list of company types to restrict who can see documents on this teardown. Allowed: Airline / Lessor / OEM / MRO / Distributor / Others. Case-insensitive. See audience.

File rules

  • Max size: 50 MB per file.
  • Allowed types: PDF, XLSX, XLS, DOCX, DOC, CSV, JPEG, PNG, WEBP, GIF.
  • One file per call. Loop client-side for batch uploads.

Storage path

Files land at:
The 8-character prefix randomises the path so naming collisions are impossible.

Response

200 OK:
The URL is also appended to teardown.documents[] automatically no separate PATCH needed.

Audience write happens BEFORE the upload

If you send an invalid audience value, you get 422 invalid_audience before the file is uploaded. No orphan storage paths.
Sending the same audience the teardown already has is a no-op no audit row written.

Delete by URL

Removes a single document URL from the teardown’s documents[]. Best-effort deletes the underlying storage file.

Query parameters

string
required
The full document URL (URL-encoded).

Response

200 OK:
Idempotent deleting a URL that isn’t present returns 200 too. The storage delete is best-effort; failures are logged but never fail the call.

See also