Skip to main content
The lead endpoints authenticate as a source. Everything else in the API, starting with customers, authenticates with an API key that belongs to your account. Use one when your CRM, Zapier, or your own code needs to create or look up customers without anyone logging in to Juiced.
API keys are available on paid plans. Only admins can see, create and revoke them.

Create a key

API Keys page under Configure, Connections, listing a GoHighLevel key that can read and create customers and a Zapier lookups key that can read customers, with each key's masked value, creator, last used time, expiry and a revoke buttonAPI Keys page under Configure, Connections, listing a GoHighLevel key that can read and create customers and a Zapier lookups key that can read customers, with each key's masked value, creator, last used time, expiry and a revoke button
  1. Open Configure → API Keys.
  2. Click New API key.
  3. Give it a label that says where it’s used, such as GoHighLevel or Zapier. The label shows up in your customers’ activity timelines, so you can always tell what a key changed.
  4. Choose what the key can do.
  5. Choose when it expires, or leave it set to Never.
  6. Click Create key and copy the key.
The full key is shown once. Juiced only keeps a fingerprint of it, so if you lose it, revoke it and create a new one. Store it in your tool’s secret settings, never in a shared document or in code you commit.
Keys start with jz_live_, which makes them easy to spot if one leaks into a log or a repository.

Abilities

Give each key only what its integration needs.

Use a key

Send the key as a bearer token, along with the usual JSON headers.
The key decides which account a request acts on, so every request only ever sees your own customers.

Revoke a key

The key list shows what each key can do, who created it, when it was last used and when it expires, so a key nothing has used in months is easy to spot. To revoke one, open Configure → API Keys, click the trash icon on the key’s row, and confirm with Revoke. It stops working right away. Anything still using it gets 401 errors until you give it a new key. To rotate a key without downtime, create the new key, update your integration to use it, then revoke the old one.

Errors

API key requests use the same error envelope as the rest of v1.

Safe retries

Creating a customer accepts an optional Idempotency-Key header, any string up to 255 characters, such as your CRM’s contact ID. Send the same key again within 24 hours and you get the original response back, with an Idempotent-Replayed: true header, instead of a second customer.
  • Same key, same body replays the original response.
  • Same key, different body returns 409 with idempotency_conflict.
  • The first request is still running returns 409 with idempotency_in_progress and a Retry-After header.
Idempotency keys belong to your account, not to one API key, so a retry still matches after you rotate keys.