Overview
We added API versioning to our public documentation so developers can work against a specific version without unexpected breaking changes.
What’s included
- Versioned documentation for each API version
- A version switcher inside the documentation
- Continued access to older versions with full documentation
- Version-specific changelogs that show additions, updates, and deprecations
Why this matters
- Makes integrations more predictable and stable
- Creates a clearer upgrade path to newer API versions
- Improves clarity when building and maintaining long-running systems
Key points
- No impact to existing integrations
- Supports adoption and migration between versions
- Sets the groundwork for structured API evolution and deprecation
Impact
- Better reliability for API consumers
- Lower risk of integration issues during updates
- Faster development and debugging with clearer references
How to use it
Open the API documentation, choose the version you want in the version switcher, then reference endpoints and schemas for that version.
What’s next
We’re working toward the next milestone: v3 of our APIs, with expanded capabilities, improved performance, and additional endpoints.
If you need API access, please contact us at support@flyingleapstudio.com.
