Skip to main content
Crave storefront requests are scope-aware.

​
API key scope

Each API key is tied to a specific location.
  • Use the key in X-API-Key
  • Use a matching locationId in the route
  • A mismatch can return authorization errors

​
Location scope

Most endpoints operate under: 
/api/v1/locations/{locationId}/...
Menus, carts, order times, fulfillment, and payments all depend on the selected location.

​
Session and cart scope

Ordering sessions and carts are also tied to the location context.
  • Create sessions per location
  • Do not reuse cart IDs across locations
  • Refresh or recreate sessions when carts expire
For deeper details, see:
  • /api-reference/overview/api-overview
  • /api-reference/overview/core-concepts
  • /guides/troubleshooting