Uber Direct
Connect your client's Uber Direct with a key they paste, and call its API through Operate As.
- Connects by
- Pasting a Client ID
- Category
- Shopping and household
- Services
- 1
- Tools
- Pass-through only
| Service | Key | Base URL |
|---|---|---|
| Uber Direct | uber-direct | https://api.uber.com/v1/customers/{customer_id} |
Your client also types their customer id (Shown in Uber Direct's developer settings).
Connecting
Your client makes a Client ID in their Uber Direct settings and pastes it on their link. Operate As tries it with Uber Direct before saving it, and stores it encrypted. See Services connected with an API key.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "uber-direct" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| Use the Uber Direct key you paste, with only the access you gave that key | Chosen on the provider's screen |
Pass-through
Uber Direct has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.
Add the client
In Clients, add your client and select Uber Direct. Then send them their link.
Your client connects
They paste a Client ID from their Uber Direct settings.
Find the endpoint
Pick the call from Uber Direct's own API docs. Your path is everything after https://api.uber.com/v1/customers/{customer_id}, with the parts in braces filled in from your client's account.
Send it through Operate As
Use the client's ID, the service key uber-direct and that path. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../uber-direct/deliveries" \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
A key works until your client deletes it in Uber Direct. They can paste a new one on the same link at any time, and your workflows carry on without changes.
See Keeping access alive and Removing access.
{ "status": 401, "data": { "…": "the service's own error" }, "encoding": "json"}