The major version lives in the URL path: /api/v1.

​
What can change within v1

Changes that are additive can land in v1 without notice:
  • New endpoints
  • New optional fields on a request
  • New fields on a response
  • New values in an existing enum
Your integration should tolerate all four. In particular, treat enums as open sets and ignore response fields you don’t recognise, rather than failing on them.
Breaking changes — removing a field, renaming one, tightening a constraint, or changing what an existing field means — do not happen inside a major version. They go into the next one.

​
v2

v2 is in testing. It adds end-to-end transaction support: v1 partners can list and offer, while v2 partners can drive the whole lifecycle through the API, along with webhooks, idempotency keys and scoped API keys. It will be documented here when it reaches general availability, with a migration guide.

​
v1 sunset

There is no sunset date for v1. It runs in parallel with v2. When a date is set, our commitment is:

A minimum of six months' notice

Delivered by email to the partner technical contact on file — so keep that contact current with info@instockrx.com if your team changes.
After v2 reaches general availability, v1 receives security fixes only. It will keep working, but it won’t gain features.
Planning a new integration now? Build on v1 — it’s the production version — but keep your request and response mapping in one layer rather than scattered through your codebase. That’s most of the work of a future migration.