/olx/users/offers

POST /api/olx/users/offers

Price: 5 credits

List all active offers of one OLX seller: full offer cards with title, price, category, location, photos and attributes. Supports narrowing by category and result ordering.

How to use it

List what a given OLX seller currently has for sale, on any OLX country marketplace via domain. Accepts the numeric seller id (seller.id on any offer), the user uuid or the seller's profile URL — the same identifiers as the users endpoint — and returns full offer objects, same shape as the offers endpoint. Useful for sizing a shop's assortment or tracking a dealer's inventory. Narrow with category_id and order with sort.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — OLX country marketplace domain. (default: "olx.pl"; one of: "olx.pl", "olx.ua", "olx.ro", "olx.bg", "olx.pt", "olx.kz", "olx.uz")
• user string required — Seller identifier: numeric user id, user uuid, or the seller's OLX profile URL. (examples: "31707449", "e2a6f25c-374b-4145-92fa-534805b7ce1e")
• count integer required — Max number of offers to return (min: 1; max: 1000)
• category_id integer nullable — Restrict results to this category id (>: 0)
• sort string nullable — Result ordering; source default order when omitted (one of: "relevance", "newest", "oldest", "price_asc", "price_desc")

Response

• @type string (default: "OlxOffer")
• id string required
• url string nullable
• offer_title string nullable
• description string nullable
• status string nullable
• offer_type string nullable
• is_business boolean nullable
• price number nullable
• previous_price number nullable
• currency string nullable
• price_label string nullable
• is_negotiable boolean nullable
• is_price_arranged boolean nullable
• salary_from number nullable
• salary_to number nullable
• salary_currency string nullable
• salary_period string nullable
• is_salary_gross boolean nullable
• created_at integer nullable
• refreshed_at integer nullable
• pushed_at integer nullable
• omnibus_pushed_at integer nullable
• expires_at integer nullable
• category_id string nullable
• category_type string nullable
• location object nullable
  • @type string (default: "OlxOfferLocation")
  • city_id string nullable
  • city string nullable
  • city_alias string nullable
  • district_id string nullable
  • district string nullable
  • region_id string nullable
  • region string nullable
  • region_alias string nullable
  • latitude number nullable
  • longitude number nullable
  • radius number nullable
  • zoom integer nullable
  • is_detailed boolean nullable
• seller object nullable
  • @type string (default: "OlxOfferSeller")
  • id string nullable
  • uuid string nullable
  • name string nullable
  • company_name string nullable
  • about string nullable
  • image string nullable
  • alias string nullable
  • has_business_page boolean nullable
  • is_online boolean nullable
  • created_at integer nullable
  • last_seen_at integer nullable
  • social_network_account_type string nullable
  • has_other_offers boolean nullable
• contact_name string nullable
• attributes array (default: [])
  • @type string (default: "OlxOfferAttribute")
  • key string required
  • name string nullable
  • type string nullable
  • values array (default: [])
  • label string nullable
• key_attributes array (default: [])
• images array (default: [])
• is_highlighted boolean nullable
• is_top_ad boolean nullable
• is_promoted boolean nullable
• is_b2c_ad boolean nullable
• promotion_options array (default: [])
• has_phone boolean nullable
• has_chat boolean nullable
• has_negotiation boolean nullable
• has_delivery boolean nullable
• delivery_mode string nullable
• has_gpsr_info boolean nullable
• is_phone_protected boolean nullable
• external_url string nullable
• partner_code string nullable
• shop_alias string 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 — Seller not found on this OLX domain 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.