Five Guys Ordering Locations API

Endpoint facts

Method

GET

API path

/fiveguys/ordering-locations

Auth

apiKey

Credits

1 credit/request

Charged on

Successful 2xx responses only

Platform

FiveGuys

Response schema

#/definitions/fiveguys.orderingLocationsResponseDoc

How this endpoint behaves

• they do not share store ids — id here is the ordering platform's own identifier;
• this endpoint publishes a per-store name ("Five Guys Austin Arbor") where the locator publishes the generic brand name "Five Guys";
• only this endpoint carries ordering economics and live availability.

Use /api/v1/fiveguys/nearby for addresses, hours, and amenity labels; use this endpoint for fees, minimums, and what an order placed right now could actually use.

Query parameters:

• latitude (required) — search center latitude, e.g. 30.267153.
• longitude (required) — search center longitude, e.g. -97.743061.
• radius (optional, default 20, max 50) — search radius in miles.
• limit (optional, default 10, max 50) — maximum restaurants to return.
• include_hours (optional) — set true to also return each store's dated operating calendars.
• days (optional, default 7, max 30) — how many days of calendar to return from today. Only meaningful with include_hours.

No per-item prices here. This endpoint publishes per-store fees and order minimums only. Use each result's id with /api/v1/fiveguys/ordering-menu for that store's actual priced menu.

The ordering platform rate-limits bursts. When it does, this endpoint returns 503 with a retry message rather than partial or malformed data; retry shortly.

Response includes locations[], count, radius, source_url, and fetched_at. Each location has id, store_number, slug, name, address, latitude, longitude, phone, distance_miles, is_available, availability_message, customer_message, delivery_fee, minimum_delivery_order, minimum_pickup_order, fulfillment (delivery, pickup, curbside, dine_in, drive_thru, dispatch, group_orders, coupons, loyalty, calories_displayed), advance_order_days, advance_only, supported_time_modes[], utc_offset, order_url, and (with include_hours) calendars[].

Each entry in calendars[] has a type (business for store hours, dispatch for delivery, and occasionally others the platform publishes), an optional label, and ranges[] of start/end/weekday. Starts and ends are dated, formatted YYYYMMDD HH:MM in the store's own local time and passed through unchanged. Because they are dated rather than recurring, they capture holiday and special hours that the weekly schedule on /api/v1/fiveguys/search and /api/v1/fiveguys/nearby cannot express.

Shared guides

Related