POST /api/tradeaplane/listings/search
Price: 20 credits
Search Trade-A-Plane aircraft for sale by make, model, category, condition, price, airframe total time and seller: each with asking price, registration, total time, seller and location.
Shortlist aircraft for sale, then pass an id to tradeaplane/listings for the full record. One filter combination reaches at most 3,000 listings, so split a broad search by make or category to cover more.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of listings to return (min: 1; max: 3000)make string nullable — Aircraft make as the site writes it (examples: "CESSNA")model string nullable — Aircraft model as the site writes it (examples: "172")category string nullable — Aircraft category as the site writes it (examples: "Single Engine Piston")condition string nullable — Listing condition (one of: "New", "Used", "Project", "Not Specified")price_min integer nullable — Lowest asking price in USD (min: 0)price_max integer nullable — Highest asking price in USD (min: 0)total_time_min integer nullable — Lowest airframe total time in hours (min: 0)total_time_max integer nullable — Highest airframe total time in hours (min: 0)seller_id string nullable — Seller id from a listing's seller_id (examples: "103740"; pattern: ^\d+$)sort string nullable — Result ordering (one of: "recently_updated", "price_low_to_high", "price_high_to_low", "make", "model")@type string (default: "TradeaplaneListingCard")id string requiredurl string requiredcategory string nullablemodel_group string nullableprice number nullableprice_text string nullableregistration_number string nullabletotal_time string nullabledescription string nullableimage string nullableseller_id string nullableseller_name string nullablelocation string nullableupdated_at integer nullable422 — 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 — The entity was not found, or a precondition failed 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.