Current version
The current API version is v5, accessible at:Version format
URL versioning
API versions are included in the URL path:Version header
Every API response includes aVersion header with detailed version information:
firstquadrant.ai-YYYY-MM-DD-{commitHash}
This header provides:
- Date: When this version was deployed
 - Commit Hash: The exact code version running
 
Version lifecycle
Version support policy
| Version | Status | Support End Date | Notes | 
|---|---|---|---|
| v5 | Current | - | Latest features and improvements | 
| v4 | Deprecated | 2024-12-31 | Security fixes only | 
| v3 | End of Life | 2023-12-31 | No longer available | 
Deprecation timeline
- Announcement: 6 months before deprecation
 - Deprecation: Version marked as deprecated, security fixes only
 - End of Life: 12 months after deprecation announcement
 - Removal: API version no longer accessible
 
Breaking vs non-breaking changes
Non-breaking changes (no version change)
These changes are made without incrementing the API version:- Adding new endpoints
 - Adding new optional fields to responses
 - Adding new optional parameters to requests
 - Adding new values to enums (when the client can handle unknown values)
 - Performance improvements
 - Bug fixes
 
Breaking changes (new version required)
These changes require a new API version:- Removing endpoints
 - Removing or renaming fields
 - Changing field types
 - Changing authentication methods
 - Modifying validation rules
 - Changing error response formats
 - Removing enum values
 
Checking your API version
Via cURL
Programmatically
Migration guide
Preparing for version changes
- Monitor Deprecation Notices: Subscribe to API changelog
 - Test Early: Use staging environment to test new versions
 - Gradual Migration: Update services incrementally
 - Version Abstraction: Implement version handling in your client
 
Version abstraction pattern
Version-specific changes
v5 (Current)
Released: January 2024 New Features:- Advanced filtering with dot notation
 - Cursor-based pagination improvements
 - Enhanced field selection
 - Batch operation support
 - Improved error responses
 
- Filter syntax changed from 
filter[field][op]tofilter.field.op - Removed deprecated 
/legacyendpoints - Standardized ID prefixes across all resources
 
v4 to v5 migration
Filter syntax update
Response format changes
Testing version compatibility
Version-specific test suite
Compatibility checker
Staying updated
API changelog
Monitor changes through:- Changelog: docs.firstquadrant.ai/changelog
 - Email Notifications: Subscribe to API updates
 - Version Header: Monitor the 
Versionheader for changes 
Webhooks for version changes
Subscribe to version change notifications:Best practices
1. Explicit version declaration
Always explicitly specify the API version:2. Version configuration
Make version configurable:3. Gradual migration
Implement feature flags for version migration:4. Monitor version usage
Track which versions your application uses:Summary
- Current Version: v5
 - Version in URL: 
https://api.us.firstquadrant.ai/v5 - Version Header: Included in all responses
 - Support Period: 12+ months after deprecation
 - Migration Notice: 6 months before changes
 - Best Practice: Always use explicit versioning