Authentication

Use a project API key to authenticate API requests. Keep the key in server-side configuration. Do not send it to a browser, mobile app, or public repository. Create and revoke project API keys in the Unprice Dashboard.

Bearer authentication

Send the key as a Bearer token in the Authorization header:

Authorization: Bearer unprice_live_1234567890

For example:

curl -X GET "https://api.unprice.dev/v1/plan-versions/get/{planVersionId}" \
  -H "Authorization: Bearer unprice_live_1234567890" \
  -H "Content-Type: application/json"

Keep the key safe

For a browser or mobile application, call your own server. Your server can then call the Unprice API with the key. Rotate a key if you believe that it was exposed.

Authentication errors

Missing, malformed, or inactive keys return HTTP 401 with code UNAUTHORIZED. A key-type mismatch returns HTTP 403 with code INSUFFICIENT_PERMISSIONS. Other access restrictions can return HTTP 403 with code FORBIDDEN. Each response includes a request ID. Keep this ID when you contact support. Example HTTP 401 response:

{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "The API key is missing, malformed, or not active.",
    "docs": "https://docs.unprice.dev/api-reference/errors/code/UNAUTHORIZED",
    "requestId": "req_abc123xyz789"
  }
}

Check these items first:

The request has an Authorization header.
The token uses the correct project API key.
The key is active and has permission for the requested resource.

API Documentation

Errors

Endpoints

Bearer authentication

Keep the key safe

Authentication errors

​Bearer authentication

​Keep the key safe

​Authentication errors

Bearer authentication

Keep the key safe

Authentication errors