Verb Data
Home
Search…
Verb Documentation
Release Notes
Environment Settings
Authentication
Data Sources
Ingestion Methods
Table Sync Intervals
Data Source Integrations
Models
What is a Model
Building a Model
Advanced Model Information
Data Transformations
What is a Transformation
Building Transformations
Collections
What is a Collection
Building Collections
API Collections
Building API Collections
API Collection Versions
Advanced Collection Options
Tiles
What is a Tile
Tile Management
Tile Actions
Custom Date Formats
Design Themes
What is a Design Theme
General Theme Settings
Data Visualization Settings
Account Settings
Integrations
Legal
Terms of Use
Privacy Policy
Subscription Agreement Terms
Subscription Agreement
Data Processing Addendum
Powered By GitBook
API Collection Versions
Managing API Collection versions
Verb Data Access APIs can be versioned to help your end users keep up with schema changes at their own pace.
To create a new Version of a Data Access API Collection you will edit the current API version. When your changes are ready for production you'll publish the API. During the publish process you'll have the option to overwrite the current version or create and number the new version.
When creating a new collection version, Data Access Keys with permissions will automatically have access to the new version. Their documentation will be automatically updated and available at the same link to make it simple for your end user to see the changes. You will need to notify the end user of the new version or share the key with them again.
Previous
Data Access API Documentation
Next - Collections
Advanced Collection Options
Last modified 1yr ago
Copy link