POST /api/petsplace/categories
Price: 20 credits
Pets Place category taxonomy. Returns the full two-level catalog tree: top-level groups (animal / product domain) and their leaf categories, each with a product count. Pass parent to return only the leaf categories under one top-level group.
Pets Place product-category taxonomy (NL). Each entry: id (stable category identifier — the group name for top-level entries, 'Group/Category' for leaf entries), name, parent_category_id (the top-level group a leaf belongs to; null for top-level groups), level (1 = top-level group, 2 = leaf category), product_count (number of products in that category). With no parameters the full tree is returned (top-level groups followed by their leaf categories). Set parent (a top-level group name such as 'Hond', 'Kat', 'Vogel') to return only that group's leaf categories. Use these names directly as the turnover_group / category filters of the product search endpoint.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)parent string nullable — Restrict to leaf categories under a single top-level group. Leave empty to return the full taxonomy (top-level groups and all their leaf categories). (examples: "Hond", "Kat", "Vogel")@type string (default: "PetsplaceCategory")id string requiredname string requiredparent_category_id string nullablelevel integer requiredproduct_count integer nullable422 — 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.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.