Quick Start - Teardowns.aero API

The Teardowns.aero public API lets your ERP post teardowns, manage listings, and attach documents without going through the web app. Authenticate with an API key you mint yourself on Settings → API Access, then send JSON or multipart requests over HTTPS.

What you can do

Teardowns create the teardown (aircraft or engine), update its fields, transition it through Starting / In process / Completed, attach documents and images. Listings publish whole aircraft, engines, or APUs for sale / lease / exchange. (Parts and landing-gear listings are UI-only today.) Documents and images attach files/images to either a teardown or a listing, set visibility per company-type audience. The shapes you’ll work with mirror what the web app uses internally, so anything you can do in the dashboard you can do over the API.

Base URL

https://api.teardowns.aero

Required headers

Authorization: Bearer tdao_live_<your-key>
X-Organization-Id: <your-org-uuid>

Both come from Settings → API Access in the web app. See authentication for the full validation pipeline and managing API keys for minting, rotating, and revoking.

Available endpoints

Teardowns

Method	Path	Purpose
POST	`/public/v1/teardowns`	Create a teardown
GET	`/public/v1/teardowns`	List your teardowns
GET	`/public/v1/teardowns/{teardown_id}`	Get one teardown
PATCH	`/public/v1/teardowns/{teardown_id}`	Update fields
DELETE	`/public/v1/teardowns/{teardown_id}`	Hard delete
POST	`/public/v1/teardowns/transition/{teardown_id}`	Change status

See Teardowns API reference for detailed request and response schemas.

Sales / Lease / Exchange

Method	Path	Purpose
POST	`/public/v1/sales-lease-exchange`	Create a listing
GET	`/public/v1/sales-lease-exchange`	List your listings
GET	`/public/v1/sales-lease-exchange/{listing_id}`	Get one listing
PATCH	`/public/v1/sales-lease-exchange/{listing_id}`	Update fields (including `status`)
DELETE	`/public/v1/sales-lease-exchange/{listing_id}`	Hard delete

See Listings API reference for detailed request and response schemas.

Uploads

Method	Path	Purpose
POST	`/public/v1/teardown/documents/{teardown_id}`	Attach a document to a teardown
DELETE	`/public/v1/teardown/documents/{teardown_id}/by-url`	Remove one teardown document by URL
POST	`/public/v1/teardown/images/{teardown_id}`	Attach an image to a teardown
DELETE	`/public/v1/teardown/images/{teardown_id}/by-url`	Remove one teardown image by URL
POST	`/public/v1/teardown/{doc_type}/{teardown_id}`	Slot doc (`harvest-list` / `occm` / `aircraft-details` / `non-incident-statement`)
DELETE	`/public/v1/teardown/{doc_type}/{teardown_id}`	Clear that slot
POST	`/public/v1/sales-lease-exchange/documents/{listing_id}`	Attach a document to a listing
DELETE	`/public/v1/sales-lease-exchange/documents/{listing_id}/by-url`	Remove one listing document by URL
POST	`/public/v1/sales-lease-exchange/images/{listing_id}`	Attach an image to a listing
DELETE	`/public/v1/sales-lease-exchange/images/{listing_id}/by-url`	Remove one listing image by URL

See Uploads API reference for multipart shapes, size and MIME limits, and the optional audience form field.

Concepts to know before integrating

Authentication

The two required headers and how each one is verified.

Managing API keys

Mint, rotate, revoke. Includes UI screenshots.

Vocabularies

Accepted values for aircraft_type, engine_model, and (for listings) apu_model.

Audience

Restricting who can see your attached documents.

Rate limits

The four buckets and how to recover from 429.

Errors

Every documented error code and its remediation.

​What you can do

​Base URL

​Required headers

​Available endpoints

​Teardowns

​Sales / Lease / Exchange

​Uploads

​Concepts to know before integrating