2026.36 Unique API / SDK Changes
1 min read
Unique API Documentation: Check out the documentation to learn more about how Unique API Swagger works and where to access it: https://unique-ch.atlassian.net/wiki/x/Q4A5ZQ.
SDK Documentation: https://unique-ag.github.io/ai/unique-sdk/
Unique API
Rollout — Identity & access
tech From .36, the Identity & access domain is served by the new Unique API implementation: /users, /groups, /company.
The base URL does not change. Integrations continue to work at
https://gateway.unique.app/public/chat/{resource}— no client action is required.One domain is enabled per even release,
.36through.48. Every other domain stays on the previous implementation until its own release.
Behaviour changes to expect on these resources
403 Forbidden — RBAC is now enforced. Calls from users without the required role are rejected.
400 Bad Request — stricter request validation. Payloads that do not match the new contract now fail.
422 — internal errors return a clear, accurate message instead of a generic failure.
Full rollout order, per-domain resource lists and the complete set of behaviour changes: Unique API Version 2026.03.01.
New Endpoints
None in this release.
SDK
No SDK changes in this release.