Three lines




There are three authentication mechanisms for accessing the Riders API. To begin, register an application so that you can follow along with authenticating and making requests on the API in the guides linked below. Note that you will have to sign in with an Uber account and we currently do not support organization accounts. See the FAQ for more information.

Server Token

Note: Server tokens are no longer supported and new tokens cannot be granted. Existing server tokens will continue to work until all developers are migrated to using scopes-based access tokens.

A server token can be used to access data that does not require an Uber user context. It can only be generated from the dashboard. The following Riders API endpoints can be accessed with a server token:

Method Endpoint Description
GET /products List products
GET /products/{product_id} Get product details
GET /estimates/price Get price estimates
GET /estimates/time Get time estimates
User Access Token

A user access token is required when an Uber user context is necessary, and is generated using the OAuth 2.0 flow. The following Riders API endpoints can be accessed with a user access token:

Method Endpoint Description
GET /me Get user information
PATCH /me Apply a user promotion
GET /history Get user history
GET /places/{place_id} Get a saved place
PUT /places/{place_id} Update a saved place
POST /requests/estimate Get request estimate
POST /requests Create ride request
GET /requests/{request_id} Get ride details
DELETE /requests/{request_id} Cancel request
PATCH /requests/{request_id} Update request
GET /requests/{request_id}/map Get tracking map
GET /requests/{request_id}/receipts Get receipt
Single Sign On (SSO) - For mobile apps

If you want to authenticate an Uber user on a mobile device, the best practice is to use the SSO feature in the Uber SDK. It is only available through the Android and iOS mobile SDKs.


© 2023 Uber Technologies Inc.