Get one UberEats promotion
Get one UberEats promotion, by id.
This read calls Uber Eats on each request. If Uber Eats refuses the call, it fails with a 502. It never returns a promotion in that case.
Failures beyond the document-wide codes: 404 when promotionId does not exist or belongs to another organization. The two cases are indistinguishable, as everywhere else on this API.
Safe to retry: this operation is read-only and idempotent.
Request
- promotionIdstring
Required. The
promotionIdfromcreateUberEatsPromotionorfetchUberEatsPromotions.
{
"promotionId": "00000000-0000-0000-0000-000000000000"
}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.
- promotionUberEatsPromotion
The promotion, in the same shape
fetchUberEatsPromotionsreturns.
{
"promotion": {
"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"
}
}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.