Teardowns
List teardowns
Paginated list of teardowns owned by your organization.
GET
Returns a paginated list of teardowns owned by your organization. Always org-scoped unlike the UI’sDocumentation Index
Fetch the complete documentation index at: https://teardowns.aero/docs/llms.txt
Use this file to discover all available pages before exploring further.
GET /teardowns (which returns
a cross-org active feed), this endpoint never returns another org’s
teardowns. There is no way to opt out.
Headers
Bearer tdao_live_…Your organization’s UUID.
Query parameters
Filtering
Filter by asset type:
aircraft or engine. APU and landing-gear
teardowns are UI-only — passing either returns 422. Legacy rows
with those types remain readable via the detail endpoint.Filter by aircraft-type name (e.g.
A320-200). Case-insensitive.
Unknown values return 400 unknown_vocabulary with the allowed list.
Same DX as the create endpoint no UUID lookup required.Filter by engine-model name (e.g.
CFM56-5B). Case-insensitive.Filter by status. Comma-separated list of internal status values:
active_starting, active_in_process, active_completed,
suspended, archived.Filter by country (substring match, case-insensitive). e.g.
US.Free-text search across
msn, registration, and description.
Substring, case-insensitive.Sorting
One of
created_at, msn, status, location_country,
teardown_start_date, asset_type.asc or desc.Pagination
1-indexed page number.
Page size. Minimum 1, maximum 100.
Response
200 OK. Paginated envelope:
Array of teardown summary objects (similar shape to the detail
response same field names, same partner-facing renames).
Total count of teardowns matching the filters across all pages.
Echo of the requested page.
Echo of the requested page size.
Total page count for the filtered set.
The list endpoint currently returns the legacy field names
(
id / registration / location_country) rather than the
partner-facing aliases (teardown_id / tail_number / country) the
detail endpoint uses. We’re aligning the shapes in a future release;
for now, branch on id in list responses and teardown_id in detail
responses. Both refer to the same UUID.Pagination patterns
For partners syncing all teardowns into an ERP, the typical loop:sort_by=created_at&sort_dir=desc and stop when you see a
teardown you’ve already imported. We don’t currently expose a
“created_after” filter request via support if you need one.
See also
- Get one teardown for full detail.
- Vocabularies for the accepted names the
aircraft_type/engine_modelfilters expect. - Rate limiting for the pagination cadence your loop should use.

