/avito/items

POST /api/avito/items

Price: 20 credits

Get full Avito listing details by item ID (or listing URL): title, price (RUB), description, specification params, images, location and coordinates, category, view counts and seller with rating.

How to use it

Fetch a single Avito listing by numeric item ID or a listing URL. Returns one item with name, price (RUB, float), currency, description, params (spec key/values), category+category_id+breadcrumbs, address, location_id, coords (lat/lng), view_count, today_view_count, posted_label, image+images and seller (id/name/url/rating/review_count/is_company).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• item string required — Avito item ID or a listing URL containing it (examples: "3234391224", "https://www.avito.ru/kaliningrad/telefony/iphone_13_128_gb_sim_esim_3234391224"; minLength: 1)

Response

• @type string (default: "AvitoItem")
• id string required
• url string required
• name string nullable
• price number nullable
• currency string (default: "RUB")
• description string nullable
• params object (default: {})
  • * string
• category string nullable
• category_id string nullable
• breadcrumbs array (default: [])
• address string nullable
• location_id string nullable
• coords object nullable
  • @type string (default: "AvitoCoords")
  • lat number nullable
  • lng number nullable
  • address string nullable
• view_count integer nullable
• today_view_count integer nullable
• posted_label string nullable
• image string nullable
• images array (default: [])
• seller object nullable
  • @type string (default: "AvitoItemSeller")
  • id string nullable
  • name string nullable
  • url string nullable
  • rating number nullable
  • review_count integer nullable
  • is_company boolean (default: false)

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 — Item not found (well-formed but nonexistent/removed item 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.