/olx/categories

POST /api/olx/categories

Price: 20 credits

Get the full OLX category tree for a country marketplace: every category with id, name, alias, parent_id, depth level, child ids, browse URL and the current number of live offers in it.

How to use it

Fetch the complete OLX category tree for one country marketplace (domain). Returns a flat list of up to roughly 3000 categories; each has id (use as category_id in offers/search), name, alias, parent_id (null for top-level departments), level, child_ids, url, image and offer_count — the live number of ads in that category, which makes this a market-size snapshot as well as a lookup table. Narrow the output with parent_id (direct children only) or level (1 = top-level departments).

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")
• count integer required — Max number of categories to return (min: 1)
• parent_id integer nullable — Return only the direct children of this category id (min: 0)
• level integer nullable — Return only categories at this depth (1 = top level) (min: 1)

Response

• @type string (default: "OlxCategory")
• id string required
• name string nullable
• alias string nullable
• parent_id string nullable
• level integer nullable
• position integer nullable
• category_type string nullable
• view_type string nullable
• path string nullable
• url string nullable
• image string nullable
• child_ids array (default: [])
• offer_count integer nullable
• is_private_business boolean nullable
• photos_max integer 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 — 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.