Skip to main content
PATCH
/
public
/
v1
/
sales-lease-exchange
/
{listing_id}
curl -X PATCH "$base_url/public/v1/sales-lease-exchange/$listing_id" \
  -H "Authorization: Bearer $api_key" \
  -H "X-Organization-Id: $org_id" \
  -H "Content-Type: application/json" \
  -d '{"price_usd": 225000}'

{
  "id": "df1e...",
  "price_usd": 225000,
  ...
}

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.

PATCH a listing your organization owns. Sparse only fields on the request body are written. Omitted fields are untouched.

​
Headers

​
Authorization
string
required
Bearer tdao_live_…
​
X-Organization-Id
string
required
Your organization’s UUID.
​
Content-Type
string
required
application/json

​
Path parameters

​
listing_id
string (UUID)
required

​
Body

Every field is optional. Common fields you’ll update:
​
title / description / msn / condition
string
​
price_usd
number
​
country
string
ISO country code.
​
manufacturer / part_number
string
​
cycles_remaining
number
​
audience
array | null
Restrict (or clear) document visibility. Pass null to clear. See audience.
​
status
string
One of active, under_offer, sold, leased, exchanged, suspended, archived, draft, pending_review. PATCH is the only way to change a listing’s status today there’s no separate transition endpoint for listings.
​
aircraft_type / engine_model / apu_model
string
Re-classify by name (e.g. A320-200). Case-insensitive same resolution as the create endpoint. APU and landing-gear vocab fields aren’t supported via the public surface beyond the three listed here landing-gear classification cannot be set via the API.
​
images / documents
array of URLs
Direct overwrite. Usually you want the upload / delete-by-url endpoints instead.

​
Response

200 OK. The updated listing in the same shape every GET returns. 
curl -X PATCH "$base_url/public/v1/sales-lease-exchange/$listing_id" \
  -H "Authorization: Bearer $api_key" \
  -H "X-Organization-Id: $org_id" \
  -H "Content-Type: application/json" \
  -d '{"price_usd": 225000}'

{
  "id": "df1e...",
  "price_usd": 225000,
  ...
}

​
Audit trail

PATCH writes:
  • listing.updated generic with previous_state and new_state.
  • listing.audience.set or listing.audience.changed when audience is touched. Two separate codes so support can filter first-time restriction vs subsequent change.

​
See also