crisphive

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. Keys don’t expire — rotate them from the dashboard when needed.

Scopes

API keys currently carry full access. Scoped permissions are on the roadmap; when they ship, a key without explicit scopes keeps behaving as full-access.

Pagination & sync feed›Next