Versioning
How the Raid AI API evolves, and how to build forward-compatible clients.
Backward-compatible by default
We evolve the API additively. The following changes are considered backward-compatible and may ship at any time without a version change:
- Adding new endpoints
- Adding new optional request parameters
- Adding new fields to a response object
- Adding new values to an existing enum (for example, a new
verdictor generator name) - Changing the order of fields in a response
Build forward-compatible clients
Your integration should ignore unknown fields and tolerate new enum values rather than failing on them. Deserialize responses leniently and don't assume the set of fields or enum members is fixed.
Breaking changes
Changes that could break existing clients — removing or renaming a field, changing a field's type, or removing an endpoint — are not made to the current version. If such a change is ever required, it will be released under a new, clearly documented version, and the existing behavior will continue to be supported during a migration window.
Staying informed
Material changes are announced ahead of time. For questions about upcoming changes, reach out via Support.