A typical API evolves over time: you may add or remove resources, change them, etc... But you don't want to break your API's clients, who typically expect a certain set of resources to be available.
API versions are a way to solve this problem. Each API can have more than one API version, each one containing its own set of resources.
| Name|| Type|| Required|| Description|
| ident|| integer|| Y|| The unique identifier for this object|
| ts|| timestamp|| Y|| The date and time when this object was created or last modified|
| name|| string(50)|| Y|| The name for this API version. This must be a short name, valid in a URL, so use only letters, numbers, dash, period and underscore.|
| comments|| string(1000)|| N|| |
| project_ident|| integer|| Y|| The ident of the project/API that contains this API version|