/machinio/listings

POST /api/machinio/listings

Price: 5 credits

Get one Machinio machinery listing by id: price, condition, year, manufacturer and model, the spec table, photos, location and the selling dealer.

How to use it

Read the full record of a used machine on Machinio. Pass an id from machinio/listings/search or the number at the start of a machinio.com/listings URL; auction lots in search that link to another site have no record here.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Machinio listing id or a machinio.com/listings URL (examples: "115759613", "https://www.machinio.com/listings/115759613-2021-xcmg-xe18u-mini-excavator-in-layton-ut"; minLength: 1)

Response

• @type string (default: "MachinioListing")
• id string required
• url string required
• name string nullable
• alternate_name string nullable
• description string nullable
• category string nullable
• breadcrumbs array (default: [])
• condition string nullable
• manufacturer string nullable
• model string nullable
• year integer nullable
• stock_number string nullable
• location string nullable
• price number nullable
• price_currency string nullable
• price_text string nullable
• availability string nullable
• specs array (default: [])
  • @type string (default: "MachinioSpec")
  • name string required
  • value string required
• images array (default: [])
  • @type string (default: "MachinioListingImage")
  • url string required
  • thumbnail_url string nullable
• video_url string nullable
• seller object nullable
  • @type string (default: "MachinioListingSeller")
  • name string required
  • alias string nullable
  • url string nullable
  • location string nullable
  • rating number nullable
  • is_trusted_seller boolean nullable

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 Machinio 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.