Authentication
Every request to /api/v1/* must include a valid API key. Unauthenticated requests receive 401 Unauthorized.
For response schemas and status codes, see the API reference.
Authorization header
Send your key as a Bearer token:
Authorization: Bearer nory_live_sk_<your-secret-token>
In the API reference, use Authorize and enter the full key (including the nory_live_sk_ prefix).
Key format
| Property | Value |
|---|---|
| Prefix | nory_live_sk_ |
| Type | Secret key — treat like a password |
Keys are brand-scoped. A key only grants access to data for the brand it was issued to.
Invalid or missing keys
Missing, malformed, revoked, or incorrect keys return 401 with type: authentication_error. The response includes a WWW-Authenticate: Bearer header.
See Errors for how error responses are structured.
Security best practices
- Server-side only — never expose your secret key in client-side code, mobile apps, or public repositories.
- Environment variables — load the key from a secrets manager or environment variable, not hard-coded strings.
- Rotate on compromise — if a key is exposed, contact Nory immediately to revoke it and issue a replacement.
- One key per integration — use descriptive key names so you can identify and revoke individual integrations.
Key lifecycle
| Action | How |
|---|---|
| Obtain a key | Contact your Nory account manager |
| Revoke a key | Contact Nory — revoked keys stop working immediately |
| Replace a lost key | Request a new key; revoke the old one |
Partners cannot manage their own keys. Where an integration supports it, the customer creates and revokes the key from their own Nory account; otherwise Nory does it on request.