/machinio/companies/listings

POST /api/machinio/companies/listings

Price: 20 credits

List the machinery a Machinio dealer or seller has for sale: each with asking price, key specs, location and photo.

How to use it

Read one dealer's inventory on Machinio. Pass the alias from machinio/companies/search or machinio/companies, then pass a row id to machinio/listings for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Machinio company alias or a machinio.com/company URL (examples: "alsa-srl", "https://www.machinio.com/company/alsa-srl"; minLength: 1)
• count integer required — Max number of listings to return (min: 1; max: 500)

Response

• @type string (default: "MachinioListingCard")
• id string required
• url string nullable
• is_machinio_listing boolean required
• is_auction boolean required
• is_trusted_seller boolean required
• is_promoted boolean required
• is_paid_listing boolean required
• is_partner boolean required
• cta_state string nullable
• price number nullable
• price_currency string nullable
• price_text string nullable
• location string nullable
• description string nullable
• image string nullable
• seller_rating number nullable
• specs array (default: [])
  • @type string (default: "MachinioCardSpec")
  • name string required
  • value string required

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 company with this alias 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.