/tradeaplane/listings

POST /api/tradeaplane/listings

Price: 5 credits

Get one Trade-A-Plane aircraft listing by id: price, registration and serial numbers, location, airframe and engine times, seller, and the seller's avionics, airframe, engine and interior write-ups.

How to use it

Read the full record of an aircraft for sale on Trade-A-Plane. Pass an id from tradeaplane/listings/search or the listing_id in a trade-a-plane.com URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Trade-A-Plane aircraft listing id or a trade-a-plane.com listing URL (examples: "2460419", "https://www.trade-a-plane.com/search?listing_id=2460419&s-type=aircraft"; minLength: 1)

Response

• @type string (default: "TradeaplaneListing")
• id string required
• url string required
• sale_status string nullable
• year integer nullable
• make string nullable
• model string nullable
• registration_number string nullable
• serial_number string nullable
• location string nullable
• price number nullable
• price_currency string nullable
• price_note string nullable
• price_text string nullable
• seller_id string nullable
• seller_name string nullable
• specs array (default: [])
  • @type string (default: "TradeaplaneListingSpec")
  • name string required
  • value string required
• description string nullable
• avionics_equipment string nullable
• airframe string nullable
• engines_mods_prop string nullable
• interior_exterior string nullable
• remarks string nullable
• additional_classifications array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No Trade-A-Plane aircraft listing with this id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.