Store locator and footprint mapping
Usa los endpoints de Dunkin' para convertir store locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn Dunkin's public store and menu data into structured JSON — a directory browse across all 44 US states Dunkin operates in, coordinate-based proximity search with distance and amenity labels, full per-store detail including active third-party delivery platforms, and the national menu catalog. Credential-free.
Browse Dunkin's store directory, find nearby stores by coordinate, and get the national menu and full store detail as structured JSON.
Familias de endpoints
4
Parámetros documentados
11
Ejemplos
4
Snapshot en vivo del catálogo
Endpoints activos
4
Métodos
GET
Parámetros obligatorios
7
Referencias de esquema
4
{
"platform": "Dunkin'",
"endpoint": "dunkin-nearby",
"method": "GET",
"path": "/dunkin/nearby",
"auth": "apiKey"
}Casos de uso
Browse Dunkin's store directory, find nearby stores by coordinate, and get the national menu and full store detail as structured JSON.
Usa los endpoints de Dunkin' para convertir store locator and footprint mapping en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Dunkin' para convertir delivery-platform coverage research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Dunkin' para convertir menu content monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Dunkin' para convertir local retail presence monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Dunkin' — 4 endpoints, 11 parámetros de solicitud documentados y 4 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
4 documented Dunkin' endpoints, grouped into 4 request families — Directory, Menu and Nearby, plus 1 more.
11 request parameters are documented across those Dunkin' endpoints, 7 of them required — the full input contract is public before you write any integration code.
4 of the 4 Dunkin' endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Dunkin' 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.
4 hosted MCP tools back the Dunkin' endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/dunkin/directory
/dunkin/menu
/dunkin/nearby
/dunkin/store
Catálogo de endpoints
/dunkin/nearbyReturns Dunkin restaurants within a radius of a latitude/longitude, ordered nearest first, each with its distance in miles and kilometres, full address, phone, coordinates, the published week of hours, whether it's permanently closed, amenities, payment methods, pickup/delivery service types, which third-party delivery platforms are active, its Google Place id, timezone, and website/menu/order URLs. This is the proximity search the directory browse cannot do -- GET /dunkin/directory walks a state to city to store tree, which requires knowing the administrative path in advance. Each result carries the store id as `path`, which GET /dunkin/store also takes, so the two chain directly. `total_in_radius` reports how many stores fall inside the radius overall, which is usually far more than one page; use `offset` to walk it. A coordinate with no Dunkin nearby returns an empty list rather than an error.
Herramienta MCP dunkin_nearby
/dunkin/directoryReturns one level of Dunkin's store directory tree. Omit path for the root, which lists every US state Dunkin operates in; pass a state's path (e.g. "ny") to list its cities, or a state/city path (e.g. "ny/new-york") to list its stores. Each child carries its name, path, URL and how many stores sit under that branch. A child with is_store true is a store rather than another directory level -- pass its path (a store id) to GET /dunkin/store. This is a directory browse, not a proximity search: use GET /dunkin/nearby for a radius lookup.
Herramienta MCP dunkin_directory
/dunkin/storeReturns one Dunkin store: name, full postal address, phone, coordinates, opening hours for every day of the week, whether it's permanently closed, amenities (curbside pickup, drive-thru, wifi, kosher, turbo oven, K-Cup pods), Dunkin's own free-text feature labels, accepted payment methods, pickup/delivery service types, which third-party delivery platforms are active, the Google Place id, and the store's website/menu/order URLs. path is a store id -- from a /dunkin/directory child with is_store true, a /dunkin/nearby result's path, or the trailing digits of a dunkindonuts.com store URL. An unknown id returns a 404.
Herramienta MCP dunkin_store
/dunkin/menuReturns Dunkin's national menu: item names, descriptions and photos grouped into categories (Iced Drinks, Hot Drinks, Frozen Drinks, Sandwiches & Wraps, Savory Bites, Donuts & Bakery, Snacks and Sides). Dunkin publishes one shared menu across every US store, so this takes no store parameter. Does not carry prices or nutrition -- pricing varies by market/franchisee and isn't part of this content.
Herramienta MCP dunkin_menu
APIs relacionadas
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
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.
Cómo hacer scraping de Dunkin'
Crawlora's Dunkin' endpoints return normalized public Dunkin' store and menu data as JSON with one API key — no Dunkin' account required. Dunkin' publishes one shared national menu (names, descriptions, and photos) but no price or nutrition data through this source.
Pass a latitude and longitude to /dunkin/nearby for stores within a radius, ordered nearest first, each with distance in miles and kilometres, the published week of hours, Dunkin's own amenity labels, and which third-party delivery platforms are active there.
Call /dunkin/directory with no path for the root — the 44 US states Dunkin operates in — then pass a child's path to descend from state to city to store, useful when you need to enumerate stores by administrative region rather than a coordinate.
Pass the path from either a /dunkin/nearby result or a /dunkin/directory entry flagged is_store to /dunkin/store for that location's name, address, phone, coordinates, hours, and feature labels — passing a directory path (not a store path) returns a 404 rather than a hollow record.
Call /dunkin/menu with no parameters for Dunkin's single shared menu across every US store — item names, descriptions, and photos grouped into categories. There's no price or nutrition data; see a /dunkin/store result's menu_url for a link to that specific store's own ordering page if pricing is needed.
/dunkin/nearby's total_in_radius reports how many stores fall inside the radius overall, usually more than one page — use offset to walk the full set for a dense metro area.
Preguntas frecuentes
Call /dunkin/nearby with a coordinate for nearby stores ordered by distance, /dunkin/directory to browse the state-to-city-to-store tree, /dunkin/store with a store path for full detail, or /dunkin/menu for the national menu — all return structured JSON with one API key.
Partially. /dunkin/menu returns Dunkin's one shared national menu — item names, descriptions, and photos grouped into categories — but no price or nutrition data; pricing varies by market and franchisee and isn't part of this content.
44 states at the root of /dunkin/directory — each with its own cities and stores beneath it in the tree.
Yes — both /dunkin/nearby and /dunkin/store return which third-party delivery platforms Dunkin' marks active for that specific store.
No — Dunkin' publishes one shared menu across every US store, confirmed live across stores in different states referencing the same underlying menu id, so /dunkin/menu takes no store id and always returns the same catalog regardless of location.