Tiffany & Co. Filter Values API

Endpoint facts

Method

GET

API path

/tiffany/filters

Auth

apiKey

Credits

1 credit/request

Platform

Tiffany & Co.

Response schema

#/definitions/tiffany.filtersResponseDoc

Overview

Lists every value tiffany-search's and tiffany-category's material, gemstone, color, product_type, gender, and designer filter parameters accept, each with a live product count -- resolves the discovery gap those parameters would otherwise leave as "find one on the live site's own filter sidebar". 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.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Each top-level field (`material`, `gemstone`, `color`, `product_type`, `gender`, `designer`) lists the values accepted by the matching query parameter of the same name on `tiffany-search` and `tiffany-category`. - `product_count` is the live count of catalog items carrying that value as of `fetched_at`. - These value spaces are large (dozens to over a hundred entries per field) and shift as Tiffany's own merchandising changes, so they are documented here by discovery rather than enumerated in `tiffany-search`/`tiffany-category`'s own docs. Example response: ```json {"code":200,"msg":"OK","data":{"fetched_at":"2026-09-10T12:00:00Z","material":[{"value":"18k Yellow Gold","product_count":466},{"value":"Platinum","product_count":234},{"value":"Sterling Silver","product_count":519}],"gemstone":[{"value":"Diamond","product_count":92},{"value":"Round Brilliant Diamonds","product_count":644}],"color":[{"value":"Rose Gold","product_count":314},{"value":"Yellow Gold","product_count":393}],"product_type":[{"value":"Bracelet","product_count":219},{"value":"Ring","product_count":334}],"gender":[{"value":"MENS","product_count":12},{"value":"UNISEX","product_count":537},{"value":"WOMENS","product_count":461}],"designer":[{"value":"Elsa Peretti®","product_count":727},{"value":"Paloma Picasso®","product_count":65}]}} ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related