Unique AI Documentation

Unique API Version 2026.03.01

2 min read

Summary

We are rolling out a new Unique API (formerly Public API) version — a significant improvement focused on security, reliability, and developer experience.

The base URL does not change. Your integration will continue to work at https://gateway.unique.app/public/chat/{resource} (and https://gateway.unique.app/unique-api/{resource} for the new standalone service).

This rollout does not require any client action. The new implementation is enabled progressively — first internally, then environment by environment, then client by client — until it fully replaces the old version. Your integration, base URL, API key, and auth all remain unchanged throughout.

The one exception: if you want early access to endpoints that only exist in the new Unique API, you can opt in ahead of your normal rollout wave by setting the x-api-version request header to the new version. *for CMTs the service needs to be deployed first

🔄 Rollout Stages

The new version is enabled step by step, in this following order. Each step is validated before moving to the next, so issues are caught early and affect the smallest possible group.

Stage

Sprint

What it means

Environments & Rollout

🚀 Experimental

Sprint .30 — done

Enabled internally on QA. No client impact.

  • QA

🟢 Beta

Sprint .32 — current

Enabled on QA and UAT, then progressively on production and select client environments (see rollout order below).

  • UAT1

  • 📺

  • Unique Prod

🎯 GA

Sprint .34 or .36 (depending on Beta findings)

Progressive rollout to all clients in phases, starting with Capstone. Once complete, the old implementation is retired.

Phase 1 (STs)

  • 🍔

  • TBD

Phase 2 (STs)

  • TBD

Phase 3 (CMTs)

  • TBD

What has Changed

The new version offers the same features you're used to and has been thoroughly tested to ensure a smooth transition. That said, a few behavior changes could cause previously-succeeding calls to fail once the new version reaches your environment:

  1. Role-based access control (RBAC) is now enforced — calls made by users without the required permissions will now be rejected with a 403 Forbidden.
    If you see this: it indicates your user is missing a required role or permission. Contact your account team if you believe you should have access.

  2. Stricter request validation — requests that don't conform to the new validation rules will now fail with a 400 Bad Request.
    If you see this: check the Swagger docs for the correct schema — a field or value in your payload likely doesn't match the new contract. Check the error message for more details.

  3. Improved error handling — internal errors now return a 422 with a clear, accurate error message instead of a generic failure, making issues easier to identify and fix.

Other changes to keep in mind:

  • chatCompletions API now requires user mandatory

Questions & Support

If you have questions or run into issues once the new version reaches your environment, reach out to:

  • Your customer success manager

  • Or open a support ticket referencing "Unique API Rollout"

Last updated