Live GB Uber Eats order-history reads require an ajar API key with Uber Eats read access and a current signed-in Uber Eats iOS app session. ajar does not offer Uber Eats sign-in, token import, or renewal. Access is limited to callers who already have an approved app-session handoff.
Keep the native session on your device. Encode its JSON as base64url without padding and send it in x-uber-eats-session alongside Authorization: Bearer YOUR_AJAR_API_KEY. The session JSON contains access_token, expires_at_epoch_s and reviewed native headers. Treat the entire value as a secret and send it only over HTTPS. ajar processes it for this request and does not store it.
Call uber_eats.order_history.list with {} for up to ten recent orders. A later page requires both cursor and last_workflow_uuid. The app capture has not established how to derive the latter reliably, so only the first page is certified. Obtain a fresh app session after expiry or rejection.
Restaurant search, menus, item options, cart, checkout and tracking are Draft or absent. This connector cannot place an order or change payment methods.
Authentication guide