Three lines

Uber

Developers

Update Integration Details

PATCHhttps://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 for a partner to update its store’s integration configuration.

Authorization

OAuth 2.0 Bearer token with the eats.store scope. For more information, see Authentication.

Path Parameters
Name Type Description
store_id string Unique identifier representing a store.
Request Body Parameters
Name Type Description
integration_enabled
pos_integration_enabled
boolean (optional) Set this flag to false if you want switch off your integration. Whilst you can continue to call GET /pos_data on the store, you will lose access to most other endpoints, and you will no longer receive webhooks.

Uber or the Merchant may toggle this back on in the future; or you can do this with a user-generated access token via POST /pos_data.

If you instead want to delete your integration store data or force users to start the integration process from scratch, then use DELETE /pos_data.
is_order_manager boolean (optional) Set this flag to false if you want to resign from being the core order managing app. You will still maintain API access but will not be able to call any of the write endpoints for Order API. If you want to request to become an order manager, your merchant must do this on your behalf or you can call POST /pos_data with a user-generated access token.
integrator_store_id string (optional) Update the ID that your app uses to reference this store. This is available to retrieve via GET /pos_data; 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 GET /pos_data; 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.
Response
Status-Code: 204 No Content

Uber

Developers
© 2023 Uber Technologies Inc.