/avito/items/search

POST /api/avito/items/search

Price: 20 credits

Search Avito listings by keyword: for each result returns title, price (RUB), location and coordinates, image and seller. Supports region, category, price range, sort, seller type and category-specific filters.

How to use it

Search live Avito listings for a keyword. Returns item cards with name, price (RUB), price_string, category+category_id, location+location_id, address, coords (lat/lng), is_verified, sorted_at, image, image_count and seller (id/name/url/rating/review_count/is_company). Filter by region (slug), category (slug), price_min/price_max, sort, seller_type, delivery (Avito Delivery only) and params (category-specific attrId->value pairs).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "iphone 13", "велосипед"; minLength: 1)
• count integer required — Max number of items to return (min: 1)
• region string — Region slug scoping the search (e.g. all, rossiya, moskva, sankt-peterburg) (default: "all"; examples: "all", "moskva", "sankt-peterburg")
• category string nullable — Category slug to scope the search (e.g. telefony, avtomobili) (examples: "telefony")
• price_min number nullable — Minimum price in RUB (min: 0)
• price_max number nullable — Maximum price in RUB (min: 0)
• sort string — Result ordering (default: "default"; one of: "default", "price_asc", "price_desc", "date")
• seller_type string — Filter by seller type (default: "any"; one of: "any", "private", "company")
• delivery boolean — Only listings that offer Avito Delivery (default: false)
• params object nullable — Category-specific attribute filters as attrId->value pairs (condition, brand, memory, etc.) (examples: {"110395":"2850685"})
  • * string

Response

• @type string (default: "AvitoItemCard")
• id string required
• url string required
• name string nullable
• price number nullable
• currency string (default: "RUB")
• price_string string nullable
• category string nullable
• category_id string nullable
• location string nullable
• location_id string nullable
• address string nullable
• coords object nullable
  • @type string (default: "AvitoCoords")
  • lat number nullable
  • lng number nullable
  • address string nullable
• is_verified boolean (default: false)
• sorted_at integer nullable
• image string nullable
• image_count integer nullable
• 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 — 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.

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.