Skip to main content
A zone is a geographic area defined by a polygon boundary. Zones model where delivery is available and let you apply zone-based rules and associate areas with the store locations that serve them.

What a zone is

A zone is created from a polygon boundary and can be associated with one or more store locations. Each zone can carry:
  • A name and an optional external ID for mapping to your own systems
  • One or more store location associations, optionally with start and end dates
  • A coverage area that defines the polygon boundary
  • Free-form tags and metadata for your own classification
Create a zone with Create a zone (POST /v1/zones) and retrieve one — including its polygon boundary and associated store locations — with Get zone (GET /v1/zones/{id}). You can also list zones with pagination (GET /v1/zones) or look one up by your own identifier with Get zone by external identifier.
Zone restrictions are a separate concept layered on top of zones. A zone restriction defines a rule that controls delivery behavior within a specific zone — for example, provider restrictions or time-based rules. List them with GET /v1/zone-restrictions.

Coverage lookups

Coverage lookups answer the question “which zones contain this location?” by testing a geographic point against your zones’ polygon boundaries. Use Get zones that cover a specified location (GET /v1/zones/coverage). You can query by:
Provide both latitude and longitude to find zones whose polygons contain that exact point.
GET /v1/zones/coverage?latitude=37.76&longitude=-122.43
The endpoint returns the list of zones that cover the requested location.
If you query by latitude, you must also provide longitude (and vice versa) — coordinate lookups require both values.

Zones vs. store locations

Zones and store locations are distinct but related:
  • A store location is a physical origin — a restaurant, warehouse, or store — that deliveries depart from.
  • A zone is a geographic area, defined by a polygon, where delivery is available. A zone can be associated with one or more store locations.
Together they let you describe which store serves which area: associate a zone with a store location, and a coverage lookup tells you whether a given dropoff point falls inside that store’s delivery area. Store locations have their own coverage lookup, Get store locations that cover a specified latitude and longitude, which returns the store locations serving a point rather than the zones containing it.

Next steps

Create a zone

Define a delivery area from a polygon boundary.

Coverage lookup

Find zones covering a latitude/longitude or city/zip.

Get zone

Retrieve a zone’s boundary and store locations.

Store locations

Manage the origins that zones serve.