List UberEats promotions
List the UberEats promotions your organization's storefronts are running, with cursor pagination.
This read calls Uber Eats on each request. If Uber Eats refuses the call, it fails with a 502. It never returns an empty page in that case.
Per store, only UberEats' first page. UberEats' own list takes no paging parameter, so for each store this lists the promotions on the first page UberEats serves, and a promotion past that page is not listed. states and promotionIds filter that set, and page pages through it across your stores.
Order. Store by store, in the order of storeIds (or of your organization's Uber Eats stores when you omit it); within one store, newest createdAt first, then promotionId. A promotion with no createdAt comes last in its store.
A shared storefront is listed once. When several of your stores are connected to the same Uber Eats storefront, its promotions are listed once, under one of those stores' ids.
With no storeIds, stores that are not connected to an Uber Eats storefront are skipped, and so is a store Uber Eats cannot list; naming such a store in storeIds is a 404.
Failures beyond the document-wide codes: 404 when any storeId is not a store of your organization. An unknown id and another organization's id are indistinguishable.
Safe to retry: this operation is read-only and idempotent.
Request
- storeIdsstring[]
Only promotions on these stores. Omit for every Uber Eats store in your organization.
- promotionIdsstring[]
Only these promotions, by UberEats
promotionId. - statesstring[]
Only promotions in these states.
Possible values: [completed, active, pending, revoked, expired, deleted] - pagePageRequest
Page size and cursor.
page.limitdefaults to 50 and above 100 is a400.
{
"storeIds": [
"<storeIds>"
],
"promotionIds": [
"<promotionIds>"
],
"states": [
"completed"
],
"page": {
"limit": 50,
"cursor": "<cursor>"
}
}Responses
Headers
- x-mealco-tx-idstringoptional
The correlation id for this call, returned on every response that an operation produces, successful or not. Quote it when you report a problem so that we can trace the request. You may send your own x-mealco-tx-id on the request and it is used as the id. It is optional in the schema because a request with a malformed JSON body is rejected before an id is assigned, so that one response carries neither this header nor the txId field of the error body.
- promotionsUberEatsPromotion[]
The matching promotions.
- nextCursorstring
Pass back as
page.cursorfor the next page. Absent on the last page.
{
"promotions": [
{
"promotionId": "00000000-0000-0000-0000-000000000000",
"storeId": "00000000-0000-0000-0000-000000000000",
"promoType": "FLATOFF",
"state": "completed",
"startsAt": "2026-01-01T00:00:00Z",
"endsAt": "2026-01-01T00:00:00Z",
"createdAt": "2026-01-01T00:00:00Z",
"externalPromotionId": "00000000-0000-0000-0000-000000000000",
"currencyCode": "<currencyCode>",
"budget": {
"amount": 50,
"unlimited": true,
"period": "WEEKLY"
},
"discount": {},
"userGroup": "ALL_CUSTOMERS"
}
],
"nextCursor": "<nextCursor>"
}About Promotions
Promotions on the connected delivery platforms. Organization-scoped like every other section: the organization is the one the API key authenticates and no request field can name another.
Four operations cover the whole Uber Eats promotion lifecycle: fetchUberEatsPromotions (list), fetchUberEatsPromotion (get one, by id), createUberEatsPromotion and revokeUberEatsPromotion. There is no update and no pause on the platform, so a promotion is immutable once created.
The operations are named for the platform because the platforms differ materially: DoorDash exposes no promotion write API to integrations, and Grubhub no promotions surface at all. For both, promotion attribution arrives on the order instead (see the Orders section).
createUberEatsPromotion and revokeUberEatsPromotion are writes. A read-only API key is refused with 403.
Money is an integer in the currency's minor unit everywhere in this section: 1250 is $12.50.