POST /api/kijiji/categories
Price: 1 credit
Get the Kijiji category tree under a given category: every subcategory with its ID, localized name, parent ID and depth. Use the returned IDs as category_id when searching listings.
Fetch the Kijiji (Canada) category tree. category_id 0 returns the nine top-level departments (Buy & Sell 10, Cars & Vehicles 27, Real Estate 34, Jobs 45, Services 72, Pets 112, Community 1, Vacation Rentals 800); pass any category ID to expand that subtree. Returns a flat list of categories with id, name, parent_id and depth (0 is the requested root); rebuild the hierarchy via parent_id -> id. The ids feed category_id on kijiji/listings/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category_id integer — Root category ID of the subtree to return (0 returns the top-level tree) (default: 0; min: 0)locale string — Language of category names (default: "en"; one of: "en", "fr")@type string (default: "KijijiCategory")id integer requiredname string nullableparent_id integer nullabledepth integer (default: 0)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 — Category not found (nonexistent category 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.