Versioning
How the REST API and events are versioned, and where changes are announced.
REST API
The major version is part of the path. Every endpoint today is under /v1:
https://api.prets.app/v1/quotesThere is no version header and no way to pin your integration to a dated version. Every request gets the current /v1 behaviour.
Changes ship to /v1 continuously and are listed in the weekly API changelog, each labelled:
- Additive: new endpoints, new optional request fields, new response fields, or new enum values. Build your integration so it ignores fields and values it doesn't know.
- Deprecation: a field that still works but will be removed. Move off it.
- Breaking: a change that can break an existing integration, such as a removed field or endpoint. Breaking changes also ship within
/v1, so read each one.
Follow the changelog's RSS feed to hear about changes as they ship.
Events
Every event payload carries a version field. All events currently send:
{
"eventId": "evt_01ARZ3NDEKTSV4RRFFQ69G5AV",
"version": "2026-06-01",
"type": "quote.created",
"...": "..."
}The version changes only when the event format changes in a breaking way. Check version when you parse an event, and alert on a value you don't expect. You can't choose which version Prets sends.
Events are marked Experimental: their payloads can still change. Changes are announced in the API changelog.