Authentication

Every request to the Crisphive API is authenticated with a secret API key sent as a bearer token in the Authorization header. Create keys from your dashboard under Settings → Developers — the key value is shown once at creation, so copy it right away.

curl "https://api.crisphive.com/v1/customers" \
  -H "Authorization: Bearer chsk_test_4eC8xQ9mZ2pL7Ka0rT"

Key prefixes select the environment

The key prefix selects the data environment: chsk_live_ keys read and write production (live) data, chsk_test_ keys target the isolated sandbox. API keys expire: you choose the lifetime at creation — 30 days by default, from 1 up to 365 — and it is fixed for the life of the key; expires_at never moves. To renew, create a replacement key and revoke the old one — see Authentication.

Scopes

A key is either full-access or restricted to specific permission scopes (e.g. create job requests without read access to your customer list), and is always locked to one workspace and one environment (live or sandbox).