Skip to main content
GET
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

string
required
Bearer tdao_live_…
string
required
Your organization’s UUID.

Path parameters

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).
string (UUID)
string (UUID)
string
aircraft or engine for any teardown created through the public API. Legacy UI-created rows may still surface apu or landing_gear.
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.
string | null
string | null
string | null
string (date) | null
string (date) | null
string
Internal lifecycle value: active_starting | active_in_process | active_completed | suspended | archived.
string | null
Human label: Starting | In Process | Completed.
Yes or No.
string | null
location_city may be set on legacy rows but cannot be written via the public API.
string | null
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).
array of URLs | null
Attached image URLs.
array | null
null = “anyone with platform access”. Otherwise a non-empty list of company types.
string (datetime) | null
When the audience field was last changed.
string (datetime) | null
string (datetime) | null
Auto-archive deadline. Resets to now + 90 days on certain transitions.
string (datetime)

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