API Versions

Your API's clients typically expect a certain set of resources to be available. To prevent breaking the clients, create an API version.
lac31
APIs typically evolve over time. API versions are part of the URL of a REST endpoint, so that you can add, change, and remove resources yet preserve the existing API under an older version. An API can have more than one API version, each one containing its own set of resources. Your API's clients typically expect a certain set of resources to be available. To prevent breaking the clients, create an API version.
You can create different namespaces for different custom resources using the version name unique string value.
For more information about the portion of the URL that reflects the request you are coding, including the API version, see The API Project URL.
In this article:
2
Create API Versions
  1. With your API open, under the Create menu, click
    Versions
    .
    If you do not see this option, clear the
    Short Menu
    checkbox that appears below the menus.
  2. Click
    Add
    .
    The following image shows an example of this page:
    versions_page.png
Switch Between API Versions
  1. With your API open, in the Create section, click 
    Resources
    .
    The Resource tab displays by default.
  2. Select the version to which you want to switch from the 
    API Version
     drop-down.
Filter by API Version
You can filter by version names in the REST Lab.
 For more information about how to filter by version name, see Test your API Using the REST Lab.