Tiffany & Co. API endpoint
Use Crawlora's List Tiffany & Co. categories API to extract supported public Tiffany & Co. 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.
/tiffany/categoriesLists every category id Tiffany & Co.'s own product catalog accepts, each with a human-readable label, a kind (category for a real navigable department/subcategory, curated_shop for a curated gift/merchandising shelf), and a live product count. Each id is exactly what tiffany-category's own category parameter accepts -- resolves the category-discovery gap that parameter would otherwise leave as "find one from a storefront URL". 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 |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/tiffany/categories" \ -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.
- `kind` distinguishes a real navigable department/subcategory (`category`) from a curated gift or merchandising shelf (`curated_shop`) -- both are valid, filterable category ids on the catalog, but they serve different browsing purposes. - `label` is a human-readable label derived from `id`; it is not a precise department/subcategory split. - `product_count` is the live count of catalog items carrying that category id as of `fetched_at`. Example response: ```json {"code":200,"msg":"OK","data":{"count":279,"fetched_at":"2026-09-10T12:00:00Z","categories":[{"id":"ecommerce_us_jewelry","label":"Jewelry","kind":"category","product_count":1561},{"id":"ecommerce_us_jewelry_necklaces_and_pendants","label":"Jewelry Necklaces And Pendants","kind":"category","product_count":536},{"id":"curated_ecommerce_us_gifts_anniversary_gifts","label":"Gifts Anniversary Gifts","kind":"curated_shop","product_count":229}]}} ```
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 |
|---|---|---|
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"count": 279,
"fetched_at": "2026-09-10T12:00:00Z",
"categories": [
{
"id": "ecommerce_us_jewelry",
"label": "Jewelry",
"kind": "category",
"product_count": 1561
},
{
"id": "ecommerce_us_jewelry_necklaces_and_pendants",
"label": "Jewelry Necklaces And Pendants",
"kind": "category",
"product_count": 536
},
{
"id": "curated_ecommerce_us_gifts_anniversary_gifts",
"label": "Gifts Anniversary Gifts",
"kind": "curated_shop",
"product_count": 229
}
]
}
}Request schema
No body schema
Response schema
#/definitions/tiffany.categoriesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | tiffany.CategoriesResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].id | string | No | ID is the exact value to pass as tiffany-category's own "category" query parameter. | |||
| data.categories[].kind | string | No | Kind distinguishes a real navigable department/category ("category", ids starting "ecommerce_us_") from a curated merchandising/gift shelf ("curated_shop", ids starting "curated_ecommerce_us_") -- both are valid, filterable category ids, but they serve different purposes: see the categories endpoint documentation. | |||
| data.categories[].label | string | No | Label is a human-readable label derived from ID. | |||
| data.categories[].product_count | integer | No | ProductCount is the live count of in-index products carrying this category id, as of FetchedAt. | |||
| data.count | integer | No | ||||
| data.fetched_at | 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/tiffany/categories" \
-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