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

Headers

string
required
Bearer tdao_live_…
string
required
Your organization’s UUID.
string
required
application/json

Path parameters

string (UUID)
required

Body

Every field is optional. Common fields you’ll update:
string
number
string
ISO country code.
string
number
array | null
Restrict (or clear) document visibility. Pass null to clear. See audience.
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.
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.
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.

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