Andtradition APIandtradition.com ↗
Access &Tradition's full product catalog via API. Retrieve 410+ furniture, lighting, and objects with specs, variants, designer info, and photos.
What is the Andtradition API?
The &Tradition API exposes two endpoints covering the brand's full product catalog of 410+ items, including furniture, lighting, and decorative objects. list_products returns pageable summary data for every item in the catalog with optional category filtering, while get_product delivers complete detail records including dimensions, materials, certifications, variant images, and structured designer attribution by product slug.
curl -X GET 'https://api.parse.bot/scraper/4445a5ca-ab9f-4fe3-916f-833cbd65ead7/list_products?category=30' \ -H 'X-API-Key: $PARSE_API_KEY'
List all &Tradition products with summary information. Returns the full catalog (410+ products) in a single response sorted alphabetically by title. Optionally filter by category tag ID (e.g. 265 for Furniture, 30 for Lighting). Each product includes its slug which can be passed to get_product for full details.
| Param | Type | Description |
|---|---|---|
| category | string | Category tag ID to filter products. Known values include: 265 (Furniture), 30 (Lighting), 1755 (Classics), 1339 (EU Ecolabel), 1657 (New Collection), 41 (Objects), 1792 (Outdoor). Omitting returns all products. |
{
"type": "object",
"fields": {
"total": "integer count of products returned",
"products": "array of product summary objects"
},
"sample": {
"data": {
"total": 410,
"products": [
{
"id": 83305,
"url": "https://www.andtradition.com/products/numbra-ty1",
"slug": "numbra-ty1",
"tags": [
175,
30,
1657
],
"label": "Pendant",
"title": "Numbra",
"designers": [
"Teruhiro Yanagihara"
],
"full_title": "Numbra TY1",
"description": "Rooted in the elemental idea of the straight line, Numbra is Teruhiro Yanagihara’s first collection for &Tradition.",
"superscript": "TY1",
"primary_image": "https://wp.andtradition.com/wp-content/uploads/2023/08/ATD_Lifestyle-Images_Collection-2026.02_Numbra-TY1_Drawn-HM4_Momento-JH38_Ita-OS1-600x800.jpg",
"variants_count": 1,
"secondary_image": "https://wp.andtradition.com/wp-content/uploads/2023/08/ATD_Packshots_158652A595_Numbra-TY1_Lacquered-Oak-w-Aluminium_Front_Horizontal_ON-600x800.jpg"
}
]
},
"status": "success"
}
}About the Andtradition API
Catalog Listing
The list_products endpoint returns the entire &Tradition catalog in a single alphabetically sorted response. Each product summary includes a slug identifier, title, and associated category tag IDs. To narrow results, pass a category parameter using a known tag ID: 265 for Furniture, 30 for Lighting, 1755 for Classics, or 133 for additional groupings. The response includes a total count alongside the products array, making it straightforward to check catalog size per category.
Product Detail
Passing a slug from the listing response to get_product returns a full detail record. The response includes the canonical url, year of design, a label describing the product type, and a full_title with the model code. The variants array contains per-variant objects with title, description, thumbnail, an images array, and any applicable certifications. Designer credit is provided via a designers array, each entry carrying a name and slug for further lookup.
Specifications and Attribution
Product specifications — dimensions, materials, maintenance notes, and certifications — are nested within the variant-level data returned by get_product. The tags array on each product maps back to the category IDs used for filtering in list_products, allowing you to cross-reference a product's classification without a separate call. Design year (year) and the full model code in full_title are useful for provenance tracking and catalog management applications.
The Andtradition API is a managed, monitored endpoint for andtradition.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when andtradition.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official andtradition.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a searchable furniture reference tool filtered by category tag IDs like 265 (Furniture) or 30 (Lighting)
- Sync &Tradition product data including variant images and dimensions into an interior design platform
- Generate designer attribution pages by aggregating the
designersarray across products sharing a designer slug - Track the classic collection by filtering list_products with category tag 1755 and comparing design years
- Populate a product comparison tool with specifications and certifications from the variants array
- Create a visual catalog browser using the per-variant thumbnail and images arrays returned by get_product
- Monitor catalog size changes over time using the total count returned by list_products
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does &Tradition offer an official developer API?+
How does filtering work in list_products, and what category IDs are available?+
category query parameter with a numeric tag ID. Documented values include 265 (Furniture), 30 (Lighting), and 1755 (Classics). The same IDs appear in the tags array on each product returned by get_product, so you can verify a product's categories from either endpoint. Products belonging to multiple categories will appear in each relevant filtered result.Are pricing or retail availability data included in product responses?+
Does get_product return individual designer profile details beyond name and slug?+
designers array includes each designer's name and slug, but extended profile content such as biography, portrait images, or a list of other works by that designer is not currently returned. The API covers product-level attribution. You can fork it on Parse and revise to add a dedicated designer detail endpoint using the designer slug.Is the full catalog always returned in one response from list_products, or is there pagination?+
category parameter to reduce payload size.