The Uber API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. When a significant change is made to an endpoint, the version number used in the path of the resource being requested will be increased.

Example: /api/v2/authorize-get

However, some changes or additions are backwards-compatible and your applications should be flexible enough to handle them. These include:

• Adding new endpoints to the API
• Adding new attributes to the response of an existing endpoint
• Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs)