Sustainable sneaker and apparel catalog monitoring
Use Allbirds endpoints to turn sustainable sneaker and apparel catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Allbirds's public Shopify storefront into structured retail data for sustainable sneakers and apparel — full product catalog and detail with every size and color variant, collection browsing, storefront pages, recommendations, and sitemap discovery, all pinned to Allbirds's own storefront URL so no url parameter is needed. Credential-free.
Get Allbirds products, collections, pages, and recommendations as structured JSON through a pinned endpoint family — no url parameter needed.
Endpoint families
6
Documented params
30
Examples
11
Live catalog snapshot
Active endpoints
11
Methods
GET
Required params
16
Schema refs
11
{
"platform": "Allbirds",
"endpoint": "allbirds-store",
"method": "GET",
"path": "/allbirds/store",
"auth": "apiKey"
}Use cases
Get Allbirds products, collections, pages, and recommendations as structured JSON through a pinned endpoint family — no url parameter needed.
Use Allbirds endpoints to turn sustainable sneaker and apparel catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Use Allbirds endpoints to turn collection and merchandising research into repeatable API requests with documented inputs and JSON responses.
Use Allbirds endpoints to turn storefront page and sitemap discovery into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Allbirds endpoint catalog — 11 endpoints, 30 documented request parameters, and 11 published response schemas — the same catalog Docs and Playground run against.
11 documented Allbirds endpoints, grouped into 7 request families — Products, Collections and Pages, plus 4 more.
30 request parameters are documented across those Allbirds endpoints, 16 of them required — the full input contract is public before you write any integration code.
11 of the 11 Allbirds endpoints ship a recorded example response, and 11 carry a documented response schema — you can code against the real JSON before the first request.
Allbirds endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
11 hosted MCP tools back the Allbirds endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/allbirds/products
/allbirds/collections
/allbirds/pages
/allbirds/search/suggest
/allbirds/sitemap/urls
/allbirds/sitemaps
Endpoint catalog
/allbirds/storeReturns normalized storefront metadata for Allbirds (https://www.allbirds.com), sourced from credential-free storefront JSON. This endpoint is a brand-pinned wrapper around the generic Shopify store family: the storefront URL is fixed server-side, so no `url` parameter is accepted. If the vanity domain blocks `/products.json`, the service may fall back to a public `*.myshopify.com` domain discovered from the storefront page, or to the storefront's own embedded page data for storefronts that expose neither.
Response notes
- Returns the resolved source URL used for JSON requests. - Includes `myshopify_domain`, store name, currency, country, and published product/collection counts when `/meta.json` exposes them. - Blocked pages, malformed JSON, missing Shopify roots, and unavailable fallback domains return upstream errors. - If the classic `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the storefront's own pages directly and parsing their embedded structured data. When this fallback was used, `transport_mode` is `ssr_embedded`; it is omitted entirely for stores served by the classic catalog JSON. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "requested_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "domain": "www.allbirds.com", "source_domain": "www.allbirds.com", "name": "Allbirds", "currency": "USD", "country": "US", "published_products_count": 638 } } ```
MCP tool allbirds_store
/allbirds/productsReturns normalized products from Allbirds's (https://www.allbirds.com) public product catalog. The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty products array.
Response notes
- Valid empty result pages return `200` with an empty `products` array. - Product prices are normalized to decimal currency units. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - If the classic `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable (some headless storefronts on a Shopify catalog do not expose either), the service falls back to the storefront's own conventional "all products" collection page and parses its embedded search-result payload. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, `total_items`, and `total_pages`, plus additive per-product fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`). `limit` is honored as an upper bound; the underlying page size is fixed by the storefront and cannot be requested larger in fallback mode. All of the above are omitted entirely for stores served by the classic catalog JSON. - When the `ssr_embedded` fallback was used, the response may also include `facets` and `facets_stats`, mirroring the storefront's own filter sidebar for that listing. - This brand-pinned endpoint does not accept `sortBy` or facet-filter query parameters (out of scope -- use the generic `/shopify/products` endpoint with `url` set to this brand's storefront for sort/filter support). The response reuses the same shared DTO as the generic family, which carries `sort`/`filters` fields for that feature; they are always omitted here since this endpoint never populates them. `sort` allowed values (never actually returned by this endpoint, listed for schema completeness): `sortLTH`, `sortHTL`, `newest`. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "page": 1, "limit": 2, "products": [ { "id": "7188363542608", "handle": "example-product-handle", "title": "Example Product", "url": "https://www.allbirds.com/products/example-product-handle", "price": 45, "available": true } ] } } ```
MCP tool allbirds_products
/allbirds/products/{handle}Returns normalized product detail for one Allbirds (https://www.allbirds.com) product handle. The storefront URL is fixed server-side; `handle` is the product's URL slug.
Response notes
- Product prices from `.js` responses are normalized from cent values to decimal currency units. - Missing product handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing product fields return upstream errors. - If the classic product `.js` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the product detail page directly and parsing its embedded structured data (a richer Next.js data block when the storefront exposes one, otherwise the page's schema.org JSON-LD `ProductGroup`/`Product` block). When this fallback was used, the response includes `transport_mode: "ssr_embedded"` and additive fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`). `transport_mode` is omitted entirely for stores served by the classic transport. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "product": { "id": "7188363542608", "handle": "example-product-handle", "title": "Example Product", "price": 45, "images": [{"url": "https://cdn.shopify.com/example.jpg"}] } } } ```
MCP tool allbirds_product
/allbirds/products/{handle}/recommendationsReturns normalized recommended products for one Allbirds (https://www.allbirds.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.
Response notes
- Missing product handles return `404` when Shopify returns not found while resolving the seed product. - Valid empty recommendation arrays return `200` with an empty `products` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic recommendations endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the seed product's own detail page (recommendations are embedded there). When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, with the same additive product fields documented for the products endpoint. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "handle": "example-product-handle", "product_id": "6616124981328", "intent": "related", "limit": 10, "products": [{"handle": "example-related-product", "title": "Example Related Product"}] } } ```
MCP tool allbirds_product_recommendations
/allbirds/collectionsReturns normalized collections from Allbirds (https://www.allbirds.com). The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty collections array.
Response notes
- Valid empty result pages return `200` with an empty `collections` array. - Blocked pages, malformed JSON, and missing `collections` roots return upstream errors. - If the classic `/collections.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to enumerating collections from the storefront's own `collections` sitemap. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, and `title` is a best-effort derivation from the handle -- **not** the storefront's real display name. `products_count` and other classic-only fields are omitted, never fabricated. - In fallback mode, `handle` is derived from the last path segment of the collection URL and is not guaranteed unique across nested sub-collections; use the item's own `url` to identify a specific one. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "page": 1, "limit": 2, "collections": [ { "id": "278435758160", "handle": "example-collection", "title": "Example Collection", "url": "https://www.allbirds.com/collections/example-collection", "products_count": 24 } ] } } ```
MCP tool allbirds_collections
/allbirds/collections/{handle}/productsReturns normalized products from one Allbirds (https://www.allbirds.com) collection. The storefront URL is fixed server-side; `handle` is the collection's URL slug.
Response notes
- Valid empty result pages return `200` with an empty `products` array. - Missing collections return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - If the classic collection `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the collection listing page directly and parsing its embedded search-result payload. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, `total_items`, `total_pages`, plus additive per-product fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`) and may include `facets`/`facets_stats`. `limit` is honored as an upper bound only; underlying page size is fixed by the storefront in fallback mode. - This brand-pinned endpoint does not accept `sortBy` or facet-filter query parameters (out of scope -- use the generic `/shopify/collections/{handle}/products` endpoint with `url` set to this brand's storefront for sort/filter support). The response reuses the same shared DTO as the generic family, which carries `sort`/`filters` fields for that feature; they are always omitted here since this endpoint never populates them. `sort` allowed values (never actually returned by this endpoint, listed for schema completeness): `sortLTH`, `sortHTL`, `newest`. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "collection": "example-collection-handle", "page": 1, "limit": 2, "products": [ {"handle": "example-product", "title": "Example Product", "price": 45} ] } } ```
MCP tool allbirds_collection_products
/allbirds/search/suggestReturns products, collections, and query suggestions from Allbirds's (https://www.allbirds.com) credential-free predictive search Ajax endpoint. The storefront URL is fixed server-side.
Response notes
- Products and collections are normalized to the same shapes used by the product and collection endpoints. - Query suggestions include text and a storefront search URL when the storefront provides one. - Valid empty suggestion arrays return `200` with empty arrays. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "query": "wool", "types": ["product", "collection", "query"], "limit": 10, "products": [{"handle": "example-product", "title": "Example Product"}], "collections": [{"handle": "example-collection", "title": "Example Collection"}], "queries": [{"text": "wool", "url": "https://www.allbirds.com/search?q=wool"}] } } ```
MCP tool allbirds_search_suggest
/allbirds/pagesReturns normalized static pages from Allbirds (https://www.allbirds.com). The storefront URL is fixed server-side.
Response notes
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Valid empty page arrays return `200` with an empty `pages` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic `/pages.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to enumerating page handles from the storefront's own `pages` sitemap. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, and each item only carries `handle`, `url`, and `updated_at` -- no `title`, `id`, or `content`. Call the single-page endpoint per handle for full content. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "page": 1, "limit": 50, "pages": [ { "id": "54831906896", "handle": "example-page", "title": "Example Page", "url": "https://www.allbirds.com/pages/example-page", "content": "Example page content" } ] } } ```
MCP tool allbirds_pages
/allbirds/pages/{handle}Returns normalized static page detail for one Allbirds (https://www.allbirds.com) page handle. The storefront URL is fixed server-side.
Response notes
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Missing page handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic `/pages/{handle}.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the page's own HTML and parsing an embedded Contentful CMS entry. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`; `content` is plain text rendered from the page's rich-text blocks, and `id` is omitted (the source id is a Contentful entry id, not a Shopify numeric id). `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "page": { "id": "54831906896", "handle": "example-page-handle", "title": "Example Page", "url": "https://www.allbirds.com/pages/example-page-handle", "content": "Example page content" } } } ```
MCP tool allbirds_page
/allbirds/sitemapsReturns child sitemap URLs from Allbirds's (https://www.allbirds.com) `/sitemap.xml` index with inferred sitemap types. The storefront URL is fixed server-side.
Response notes
- Sitemap `type` is inferred from the child sitemap URL. - Inferred sitemap types are `products`, `collections`, `pages`, `blogs`, `agentic_discovery`, and `other`. - Blocked pages, malformed XML, and missing sitemap entries return upstream errors. Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "sitemaps": [ { "loc": "https://www.allbirds.com/sitemap_products_1.xml", "type": "products" } ] } } ```
MCP tool allbirds_sitemaps
/allbirds/sitemap/urlsReturns capped URL entries from Allbirds's (https://www.allbirds.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.
Response notes
- The service fetches matching child sitemaps from `/sitemap.xml` until `limit` URL entries is reached. - URL entries include `loc`, inferred `type`, `handle`, `lastmod`, `changefreq`, and optional `images`. - Blocked pages, malformed XML, and missing sitemap entries return upstream errors. Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.allbirds.com", "source_url": "https://www.allbirds.com", "type": "products", "limit": 2, "urls": [ { "loc": "https://www.allbirds.com/products/example-product-handle", "type": "products", "handle": "example-product-handle", "lastmod": "2026-05-31T23:31:08-07:00", "changefreq": "daily" } ] } } ```
MCP tool allbirds_sitemap_urls
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Allbirds
Crawlora's Allbirds endpoints return product, collection, page, recommendation, search suggestion, and sitemap data as normalized JSON with one API key — Allbirds's storefront URL is pinned server-side, so no account or url parameter is required.
Call /allbirds/products for Allbirds's full public product catalog with pagination, or /allbirds/collections and /allbirds/collections/{handle}/products to browse by merchandising collection.
Pass a product handle (from a /allbirds/products or collection result) to /allbirds/products/{handle} for full detail — pricing, every size and color variant, images, and availability.
Send a partial query to /allbirds/search/suggest for the same predictive product, collection, and query suggestions Allbirds's own search box shows.
Use /allbirds/pages and /allbirds/pages/{handle} for static storefront pages, or /allbirds/sitemaps and /allbirds/sitemap/urls to enumerate the storefront's indexed URLs.
FAQ
/allbirds/* pins Allbirds's own storefront URL (https://www.allbirds.com) server-side, so every call needs only your Crawlora API key — no url parameter. The same storefront is also reachable through /shopify/* by passing url=https://www.allbirds.com, which is the only way to reach this storefront's sort and filter options on /shopify/products and /shopify/collections/{handle}/products — those two parameters are not exposed on the brand-pinned routes.
No — only your Crawlora API key. Allbirds's storefront data is collected from its public, credential-free storefront surface.
Yes — /allbirds/search/suggest returns predictive product, collection, and query suggestions for a partial keyword, the same data Allbirds's own search-as-you-type box uses.
Yes — /allbirds/products/{handle}/recommendations returns related or complementary products for a given product handle, sourced from Allbirds's own storefront recommendation data.