UnifyUnits Developers

Authentication

Conversion endpoints require a Bearer API key. Discovery endpoints (/v1/categories, /v1/units, /v1/health, /openapi.json) are public.

http 
Authorization: Bearer uu_live_xxxxxxxxxxxxxxxxxxxxxxxxxx
Key format. Production keys use the uu_live_ prefix and contain 32 cryptographically random bytes. Treat them like passwords.
Do not embed API keys in public browser or mobile code. Use keys server-side only, or call public discovery endpoints without authentication.

Create an API key →

Endpoint access table

EndpointAuthentication
GET /v1/convertBearer
POST /v1/convertBearer
POST /v1/batchBearer
POST /v1/parseBearer
POST /v1/normalizeBearer
GET /v1/currency/convertBearer
POST /v1/currency/convertBearer
GET /v1/currency/ratesBearer
GET /v1/substancesBearer
GET /v1/substance/convertBearer
POST /v1/substance/convertBearer
POST /v1/unit-priceBearer
GET /v1/categoriesPublic
GET /v1/categories/:categoryPublic
GET /v1/unitsPublic
GET /v1/units/:unitPublic
GET /v1/healthPublic
GET /openapi.jsonPublic

Key rotation

Each account has one active API key. Rotating it revokes the previous key immediately, so requests that still use the old key start failing with INVALID_API_KEY. Revocation and plan changes can take up to 60 seconds to reach every edge location.

  1. Open your API keys page and rotate the key
  2. Copy the new key; it is shown only once
  3. Update the secret in your deployment and redeploy
  4. Verify traffic is flowing correctly

Because a key cannot be shared safely between environments, use a separate account for staging or development if you need an isolated key. Never reuse a key across production and development.

Account and API keys

Sign in with Google to manage your account. Each page covers one task: