Release history.
What changed, what stays the same, and what to review before your team upgrades.
2.1.0
Upcoming · Not released
Response fields and email verification
Read profile fields directly from the response and use a separate request to verify email delivery.
Read release notes2.0.0
Simpler defaults. Detail when you need it.
Core responses focus on the common task, with optional detail in deep. Review field moves, renamed fields, removals and plan requirements before changing your team’s version.
Read release notes1.0.0
Original contract
The original API contract
The name for the API contract that existed before explicit version selection. Existing teams keep its response fields and access rules while they prepare an upgrade.
Read release notesYour team keeps its saved default until an owner or admin confirms a change in Settings → API version. Requests with a X-API-Version header use that selected contract. Review the upgrade guide before making that change.