Uber Developers

Uber

Developers

Activate Integration

POSThttps://api.uber.com/v1/eats/stores/{store_id}/pos_data

Access to These APIs May Require Written Approval From Uber

Uber’s APIs are always under development and as such are subject to changes according to our Versioning & Upgrade policy. As part of Uber’s ongoing privacy improvements, we’ve updated our Developer API program with new scope access policies for third party applications. For further information, please refer to our Getting Started guides.

This endpoint allows an integration partner to set-up an Uber Eats store with an integration on behalf of the merchant.

¶ Authorization

OAuth 2.0 Bearer token with the eats.pos_provisioning scope, generated for your app by one of the merchant’s users via Uber’s OAuth login flow. For more information, see User Access Token Authentication.

¶ Path Parameters

Name	Type	Description
`store_id`	`UUID`	Unique identifier representing a store.

¶ Query Params

Name	Type	Description
`is_order_manager`	`boolean` (optional)	Set this flag to `true` if you want to nominate your app for managing the core order workflow. The order manager app is responsible for accepting; rejecting; or cancelling orders on behalf of the merchant. Most apps will be required to perform follow-up actions to complete the process: you must listen and respond to the `store.provisioned` webhook. As there can only be one order manager, if your app is eventually promoted, any existing order manager app will be demoted. Note: you should not request this flag if your app is passively observing store and order activity.
`integrator_store_id`	`string` (optional)	Update the ID that your app uses to reference this store. This is available to retrieve via API; and may also be exposed to Uber Support teams; or the merchant for reporting or support purposes.
`integrator_brand_id`	`string` (optional)	Update the ID that your app uses to reference this brand. This is available to retrieve via API; and may also be exposed to Uber Support teams; or the merchant for reporting or support purposes.
`store_configuration_data`	`JSON string` (optional)	Update your arbitrary data blob that your app uses to configure this store’s integration. Persisting this data with Uber facilitates a single source-of-truth; and allows support teams to debug variations in behaviors across stores. Disclaimer: DO NOT STORE PII IN THIS BLOB.
`merchant_store_id` ~~`partner_store_id`~~	`?string`	Integrators who are themselves the merchant can update their merchant IDs using this field.
~~`pos_integration_enabled`~~ (deprecated)	`?boolean`	This field is ignored and will be deprecated. Please do not send.

¶ Example Request

Try It Replace the <UBER_TOKEN> and {store_id} in the below request to use it a terminal.

curl --location --request POST 'https://api.uber.com/v1/eats/stores/{store_id}/pos_data' \
--header 'Authorization: Bearer <UBER_TOKEN>' \
--header 'Content-Type: application/json'  \
--data-raw '{
    "pos_integration_enabled": true
}' | jq .

Uber

Developers