Versioning
Current Version
The Odditt B2B API is currently at v1. All endpoints are prefixed with /v1/:
https://api.odditt.com/v1/trends/mixed-flows
https://api.odditt.com/v1/references/sports
https://api.odditt.com/v1/account/config
Stability
The v1 API is stable. We will not make breaking changes to existing v1 endpoints. Non-breaking changes - such as adding new fields to responses, new optional parameters, or new endpoints - may be introduced without a version bump.
What counts as non-breaking
- Adding new fields to JSON response objects
- Adding new optional query or body parameters
- Adding new endpoints
- Adding new enum values to response fields
- Changing the order of fields in a response
What counts as breaking
- Removing or renaming existing fields
- Changing the type of an existing field
- Removing or renaming endpoints
- Making an optional parameter required
- Changing the meaning of an existing parameter
Deprecation Policy
When a field or parameter is deprecated, it will be:
- Marked as
deprecatedin the API Reference - Documented with a recommended replacement
- Supported for at least 6 months after deprecation is announced
There are currently no deprecated fields in the public API.
Future Versions
If a v2 is introduced, v1 will continue to be supported for a transition period. Both versions will be available simultaneously at their respective URL prefixes.
Updated about 15 hours ago
Did this page help you?

