J.Crew API endpoint
Use Crawlora's J.Crew Categories API to extract supported public J.Crew 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.
/jcrew/categoriesLists every category and subcategory from the storefront's own header navigation, flattened into department/section/category triples -- resolves the category-discovery gap jcrew-category's own category parameter otherwise leaves as "find one from a storefront URL". Each entry's category value is exactly what jcrew-category's own category parameter accepts. Filter to one department with department (e.g. women, men); omit for every department. Departments vary slightly by site (jcrew.com has an extra "home" department factory.jcrew.com doesn't) -- see the response's own departments field for the live list. 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 |
|---|---|---|---|---|---|
| site | string | No | Storefront to list Allowed values: jcrew, factory | ||
| department | string | No | Department to filter to, e.g. women, men, boys, girls, accessories, shoes, home (jcrew only) -- omit for every department | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/jcrew/categories?site=jcrew" \ -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.
- `departments` lists every department the storefront's own navigation exposes. This varies slightly by site: `jcrew.com` has an extra `home` department `factory.jcrew.com` doesn't. - `section` groups entries the way the storefront's own nav does (typically `clothing`, `accessories`, `shoes`), matching the department tabs and sub-columns visible on the real site. - Some entries are hub-level (e.g. `womens/categories/clothing`, the section's own "All Clothing" link) rather than a true leaf subcategory -- passing one to `jcrew-category` returns a well-formed empty result, not an error, same as browsing that hub page on the real site. Example response: ```json { "code": 200, "msg": "OK", "data": { "site": "jcrew", "departments": ["women", "men", "boys", "girls", "home", "shoes", "accessories"], "categories": [ {"department": "women", "section": "clothing", "category": "womens/categories/clothing/sweaters", "label": "sweaters"}, {"department": "women", "section": "clothing", "category": "womens/categories/clothing/jeans", "label": "jeans"} ] } } ```
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": {
"site": "jcrew",
"departments": [
"women",
"men",
"boys",
"girls",
"home",
"shoes",
"accessories"
],
"categories": [
{
"department": "women",
"section": "clothing",
"category": "womens/categories/clothing/sweaters",
"label": "sweaters"
},
{
"department": "women",
"section": "clothing",
"category": "womens/categories/clothing/jeans",
"label": "jeans"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/jcrew.categoriesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | jcrew.CategoriesResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].category | string | No | ||||
| data.categories[].department | string | No | ||||
| data.categories[].label | string | No | ||||
| data.categories[].section | string | No | ||||
| data.departments | array | No | ||||
| data.fetched_at | string | No | ||||
| data.site | string | No | ||||
| data.source_url | string | 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/jcrew/categories?site=jcrew" \
-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