---
title: "Find Five Guys restaurants near a coordinate with ordering details"
method: GET
path: "/fiveguys/ordering-locations"
tags: ["FiveGuys"]
---

# Find Five Guys restaurants near a coordinate with ordering details

`GET /fiveguys/ordering-locations`

## Request

- Base URL: `https://api.crawlora.net/api/v1`
- URL: `https://api.crawlora.net/api/v1/fiveguys/ordering-locations`
- Auth: API key in header `x-api-key`

Returns Five Guys restaurants near a latitude/longitude as Five Guys' own ordering platform publishes them, with commerce detail no other endpoint in this family carries: per-store delivery fee, delivery and pickup order minimums, whether the store is currently accepting orders at all, the handoff modes an order placed now could actually use (delivery, pickup, curbside, dine-in, drive-thru, dispatch), group-order/coupon/loyalty support, how many days ahead an order may be scheduled, and the store's own order URL. Set `include_hours` to also return each store's dated business and delivery calendars -- concrete dated windows rather than the recurring weekly schedule the locator endpoints publish, so they reflect holiday and special hours a weekly schedule cannot express. This is a different upstream from GET /fiveguys/nearby, which returns the marketing/locator record: the two describe the same restaurants but do not share ids, and this one carries a per-store name ("Five Guys Austin Arbor") where the locator publishes the generic brand name. Use each result's `id` with GET /fiveguys/ordering-menu for that store's priced menu. A coordinate with no Five Guys nearby returns an empty list rather than an error.

## Query parameters

- `latitude` number, required
- `longitude` number, required
- `radius` integer
- `limit` integer
- `include_hours` boolean
- `days` integer

## Headers

- `x-api-key` string, required

## Response `200`

OK

- FiveguysOrderingLocationsResponseDoc
  - `code` integer: Code is the HTTP status code or a custom code used to indicate the result of the request @example 200
  - `data` FiveguysOrderingLocationsResponse
    - `count` integer
    - `fetched_at` string
    - `locations` FiveguysOrderingLocation[]
      - `address` FiveguysLocationAddress
        - `city` string
        - `country` string
        - `line1` string
        - `line2` string
        - `postal_code` string
        - `region` string
      - `advance_only` boolean: AdvanceOnly marks a store that takes only scheduled orders, never ASAP.
      - `advance_order_days` integer: AdvanceOrderDays is how many days ahead an order may be scheduled.
      - `availability_message` string
      - `calendars` FiveguysOrderingCalendar[]: Calendars are this store's dated operating windows, present only when include_hours was requested. Unlike the weekly recurring schedule GET /fiveguys/search and /fiveguys/nearby publish, these are concrete dated ranges, so they reflect holiday and special hours a recurring schedule cannot express.
        - `label` string: Label is the platform's display label when it publishes one, e.g. "Delivery".
        - `ranges` FiveguysOrderingCalendarRange[]
          - `end` string
          - `start` string: Start and End are published as "YYYYMMDD HH:MM" in the store's own local time, passed through unchanged rather than reinterpreted into a timezone this API would have to guess.
          - `weekday` string
        - `type` string: Type is the ordering platform's own calendar type, e.g. "business", "dispatch".
      - `customer_message` string
      - `delivery_fee` number: Ordering economics, in the store's own currency. DeliveryFee and the minimums are published as 0 when the store sets none.
      - `distance_miles` number: DistanceMiles is measured from the requested coordinate.
      - `fulfillment` FiveguysOrderingFulfillment
        - `calories_displayed` boolean
        - `coupons` boolean
        - `curbside` boolean
        - `delivery` boolean
        - `dine_in` boolean
        - `dispatch` boolean
        - `drive_thru` boolean
        - `group_orders` boolean
        - `loyalty` boolean
        - `pickup` boolean
      - `id` string: ID is the ordering platform's restaurant id.
      - `is_available` boolean: IsAvailable reports whether the ordering platform is currently accepting orders for this restaurant at all. AvailabilityMessage and CustomerMessage carry the store's own explanation when it publishes one (e.g. a delivery caveat, a temporary notice).
      - `latitude` number: Latitude/Longitude come from the ordering platform's own record.
      - `longitude` number
      - `minimum_delivery_order` number
      - `minimum_pickup_order` number
      - `name` string: Name is the ordering platform's per-store label ("Five Guys Fig @ 7th Downtown LA"), unlike the locator's generic "Five Guys".
      - `order_url` string: OrderURL is the ordering platform's own menu/order page for this store. Note it is hosted on a domain this API cannot itself read (see the endpoint description) -- it is published for handing to an end user, not for further scraping.
      - `phone` string
      - `slug` string
      - `store_number` string: StoreNumber is Five Guys' own internal store number.
      - `supported_time_modes` string[]: SupportedTimeModes are the ordering platform's own labels, e.g. "asap", "advance".
      - `utc_offset` number: UTCOffset is the store's current offset in hours.
    - `radius` integer
    - `source_url` string
  - `msg` unknown

## Other responses

- `400`: Bad Request
- `429`: Too Many Requests
- `503`: Service Unavailable

---

[API](https://skmtc.dev/crawlora/apis/crawlora-api.md) · [All operations](https://skmtc.dev/crawlora/apis/crawlora-api/llms.txt) · [OpenAPI document](https://skmtc.dev/crawlora/apis/crawlora-api/revisions/0497899e2016?raw)