> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/digital-river-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/digital-river-api/administration/dashboard/developers/api-keys/updating-your-api-version.md).
# Updating your API version
## Updating your API version on all keys
Use the **Update version on all keys** button on the Keys and versioning pane to [select a version and update all keys to that version](/digital-river-api/administration/dashboard/developers/api-keys/updating-your-api-version.md). You can select to update all API keys to the latest API version or a previous API version. When you update all keys, the API version column for standard keys and restricted keys displays the version you selected.
1. Select the environment you want to update using the **Test/Production** toggle. **Best Practices**: Install the new version in the [test environment](/digital-river-api/administration/dashboard/test-and-production-environments.md) first.
2. Click the **Update version on all keys** button to open the Update all keys dialog box.
3. Click the **Release notes** link to review the latest changes. If necessary, apply the changes to your system before you continue.
4. Select a version from the **API Version** drop-down list and click **Update all keys in test mode** or **Update all keys in production mode.**\
\
{% hint style="warning" %}
The key will not be available for immediate use. It can take up to 10 minutes for the key to fully propagate.
{% endhint %}
When the update is finished, the Standard and Restricted keys tables display the same API version for each restricted key.
## Release notes
The Release Notes link takes you to the list of API-breaking changes. New additions and non-breaking changes don’t need a new API version and will not appear on this list.