¶ Server Token authentication

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.

Your application may use a server token when accessing resources that are not specific to a user. To do this, grab your application’s server token from your application dashboard in the Auth tab, and include it in the Authorization header as type Token.

Here’s an example request, using the Products endpoint.

curl -H 'Authorization: Token <TOKEN>' \
'https://api.uber.com/v1.2/products?latitude=37.7759792&longitude=-122.41823'

This token may only be generated from the dashboard, and you can have multiple server tokens at a time. Server tokens can also be deleted from the dashboard. Deleting a server token invalidates that token from making any API requests.

Please note that your server token is considered sensitive and it is your responsibility to protect it.