Uber Developers

Remove Integration

DELETEhttps://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 developer to delete a store’s app integration. Merchants would have to start their app onboarding workflow completely from scratch should they wish to re-integrate their store with your app in the future.

If you would prefer to disable your integration on a more temporary basis, allowing Uber support or the merchant to re-enable the integration at a later point, use the PATCH /pos_data endpoint with the integration_enabled field set to false.

¶ Authorization

OAuth 2.0 Bearer token with the eats.pos_provisioning scope. For more information, see User Access Token Authentication.

¶ Path Parameters

Name	Type	Description
`store_id`	`string`	Unique Uber identifier representing a store.

¶ Example Request

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

curl --location --request DELETE 'https://api.uber.com/v1/eats/stores/{store_id}/pos_data' \
--header 'Authorization: Bearer <UBER_TOKEN>' | jq .