Skip to main content
GET
/
public
/
v1
/
teardowns
/
{teardown_id}
curl "$base_url/public/v1/teardowns/$teardown_id" \
  -H "Authorization: Bearer $api_key" \
  -H "X-Organization-Id: $org_id"

{
  "teardown_id": "3c707051-021d-4d04-a8e7-4eb254e80858",
  "org_id": "72f95f4e-65bb-41b3-8ef4-226c5a59cbc1",
  "created_by": "afdb4059-345b-4adb-b8f1-4035668f22d7",
  "asset_type": "aircraft",
  "aircraft_type": {
    "id": "c0000000-0000-0000-0000-000000000002",
    "name": "A320-200",
    "manufacturer": "Airbus",
    "category": "Narrowbody",
    "is_active": true
  },
  "tail_number": "VT-ABC",
  "msn": "12345",
  "traceability": "Delta",
  "start_date": "2026-08-01",
  "end_date": null,
  "status": "active_starting",
  "teardown_status_label": "Starting",
  "incident_related": "No",
  "description": "Posted from ERP",
  "location": "Tucson, AZ",
  "country": "US",
  "documents": [
    "https://.../teardowns-media/teardowns/3c707.../documents/ab12_specs.pdf"
  ],
  "images": null,
  "audience": ["Airline", "MRO"],
  "audience_set_at": "2026-05-26T20:15:00Z",
  "published_at": "2026-05-26T20:06:50.677262Z",
  "expires_at": "2026-08-24T20:06:50.677262Z",
  "created_at": "2026-05-26T20:06:48.825931Z",
  "updated_at": "2026-05-26T20:15:00Z"
}

Documentation Index

Fetch the complete documentation index at: https://teardowns.aero/docs/llms.txt

Use this file to discover all available pages before exploring further.

Returns the full teardown record for one of your org’s teardowns. Cross-org access returns 404 not_found we never reveal whether the id exists in another org.

​
Headers

​
Authorization
string
required
Bearer tdao_live_…
​
X-Organization-Id
string
required
Your organization’s UUID.

​
Path parameters

​
teardown_id
string (UUID)
required
The teardown’s id (from the teardown_id field on create / list responses).

​
Response

200 OK. The same shape returned by the create endpoint partner field names (teardown_id, tail_number, start_date, country, end_date).
​
teardown_id
string (UUID)
​
org_id
string (UUID)
​
asset_type
string
aircraft or engine for any teardown created through the public API. Legacy UI-created rows may still surface apu or landing_gear.
​
aircraft_type | engine_model | apu_model | landing_gear_type
object
Whichever vocabulary row matches the asset_type, populated with { id, name, manufacturer, category, is_active }. The remaining vocabulary fields are null. apu_model and landing_gear_type appear only on legacy teardowns the public API can’t create them.
​
tail_number
string | null
​
msn
string | null
​
traceability
string | null
​
start_date
string (date) | null
​
end_date
string (date) | null
​
status
string
Internal lifecycle value: active_starting | active_in_process | active_completed | suspended | archived.
​
teardown_status_label
string | null
Human label: Starting | In Process | Completed.
​
incident_related
string | null
Yes or No.
​
location / location_city / country
string | null
location_city may be set on legacy rows but cannot be written via the public API.
​
description
string | null
​
documents
array of URLs | null
Attached document URLs. Subject to audience filtering when read by a different org (this endpoint always returns the full list since it’s org-scoped to the owner).
​
images
array of URLs | null
Attached image URLs.
​
audience
array | null
null = “anyone with platform access”. Otherwise a non-empty list of company types.
​
audience_set_at
string (datetime) | null
When the audience field was last changed.
​
published_at
string (datetime) | null
​
expires_at
string (datetime) | null
Auto-archive deadline. Resets to now + 90 days on certain transitions.
​
created_at / updated_at
string (datetime)
curl "$base_url/public/v1/teardowns/$teardown_id" \
  -H "Authorization: Bearer $api_key" \
  -H "X-Organization-Id: $org_id"

{
  "teardown_id": "3c707051-021d-4d04-a8e7-4eb254e80858",
  "org_id": "72f95f4e-65bb-41b3-8ef4-226c5a59cbc1",
  "created_by": "afdb4059-345b-4adb-b8f1-4035668f22d7",
  "asset_type": "aircraft",
  "aircraft_type": {
    "id": "c0000000-0000-0000-0000-000000000002",
    "name": "A320-200",
    "manufacturer": "Airbus",
    "category": "Narrowbody",
    "is_active": true
  },
  "tail_number": "VT-ABC",
  "msn": "12345",
  "traceability": "Delta",
  "start_date": "2026-08-01",
  "end_date": null,
  "status": "active_starting",
  "teardown_status_label": "Starting",
  "incident_related": "No",
  "description": "Posted from ERP",
  "location": "Tucson, AZ",
  "country": "US",
  "documents": [
    "https://.../teardowns-media/teardowns/3c707.../documents/ab12_specs.pdf"
  ],
  "images": null,
  "audience": ["Airline", "MRO"],
  "audience_set_at": "2026-05-26T20:15:00Z",
  "published_at": "2026-05-26T20:06:50.677262Z",
  "expires_at": "2026-08-24T20:06:50.677262Z",
  "created_at": "2026-05-26T20:06:48.825931Z",
  "updated_at": "2026-05-26T20:15:00Z"
}

​
Why 404 for foreign-org teardowns

Returning 403 would tell a probing caller that the id exists in some other org that’s a side channel for enumerating other partners’ teardowns. 404 collapses “doesn’t exist” and “not yours” into one response, so neither case leaks information.

​
See also