Hermes API endpoint
Use Crawlora's Hermès categories API to extract supported public Hermes data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/hermes/categoriesReturns every browsable Hermès category for a market: the category code hermes-category accepts, its display name, its page path and absolute URL, its parent code and its depth in the tree. This is the discovery endpoint for hermes-category's category parameter, so every accepted value is obtainable from this API rather than by reading the website. Editorial and story tiles that carry no browsable category page are excluded, so every code returned is one hermes-category will accept. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| locale | string | No | Market and language. One of: at_de, au_en, be_en, be_fr, br_pt, ca_en, ca_fr, ch_de, ch_fr, cz_en, de_de, dh_en, dk_en, es_es, fi_en, fr_fr, gr_en, hk_en, ie_en, it_it, jp_ja, kr_ko, lu_fr, mo_en, mx_es, my_en, nl_en, no_en, pl_en, pt_en, ri_en, se_en, sg_en, th_en, tw_zh, uk_en, us_en Allowed values: at_de, au_en, be_en, be_fr, br_pt, ca_en, ca_fr, ch_de, ch_fr, cz_en, de_de, dh_en, dk_en, es_es, fi_en, fr_fr, gr_en, hk_en, ie_en, it_it, jp_ja, kr_ko, lu_fr, mo_en, mx_es, my_en, nl_en, no_en, pl_en, pt_en, ri_en, se_en, sg_en, th_en, tw_zh, uk_en, us_en | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/hermes/categories?locale=at_de" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- `code` is the value to pass to `hermes-category`. `path` and `url` point at the same category on hermes.com for the selected market. - `parent_code` is empty for a top-level department; `depth` is 0 there and increases with nesting. `children` counts direct subcategories. - The taxonomy is market-specific: names and paths are localized, and the set of categories can differ between markets. Example response: ```json { "code": 200, "msg": "ok", "data": { "locale": "us_en", "total": 176, "categories": [ { "code": "WOMEN", "name": "Women", "path": "/us/en/category/women/", "url": "https://www.hermes.com/us/en/category/women/", "depth": 0, "children": 8 }, { "code": "WOMEN_SHOES_SNEAKERS", "name": "Sneakers", "path": "/us/en/category/women/shoes/sneakers/", "url": "https://www.hermes.com/us/en/category/women/shoes/sneakers/", "parent_code": "WOMEN_SHOES", "depth": 2, "children": 0 } ] } } ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "ok",
"data": {
"locale": "us_en",
"total": 176,
"categories": [
{
"code": "WOMEN",
"name": "Women",
"path": "/us/en/category/women/",
"url": "https://www.hermes.com/us/en/category/women/",
"depth": 0,
"children": 8
},
{
"code": "WOMEN_SHOES_SNEAKERS",
"name": "Sneakers",
"path": "/us/en/category/women/shoes/sneakers/",
"url": "https://www.hermes.com/us/en/category/women/shoes/sneakers/",
"parent_code": "WOMEN_SHOES",
"depth": 2,
"children": 0
}
]
}
}Request schema
No body schema
Response schema
#/definitions/hermes.categoriesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | hermes.CategoriesResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].children | integer | No | ||||
| data.categories[].code | string | No | ||||
| data.categories[].depth | integer | No | ||||
| data.categories[].name | string | No | ||||
| data.categories[].parent_code | string | No | ||||
| data.categories[].path | string | No | ||||
| data.categories[].url | string | No | ||||
| data.locale | string | No | ||||
| data.total | integer | No | ||||
| msg | string | No | ok |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/hermes/categories?locale=at_de" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms