Connecting Juicebox to Kula

Juicebox is an AI sourcing tool. Its integration with Kula runs on Kula's Application API — Juicebox built and owns the integration itself, and Kula's only part is issuing the API key that lets Juicebox talk to your account.

Once connected, Juicebox can pull your Kula jobs in so a search can start straight from a job description, push sourced profiles into a chosen Kula job (landing as an application, resume attached), and flag candidates already in Kula for rediscovery in Juicebox.

Before you start: the flow starts in Juicebox

Order matters here. Don't go looking for a "Connect Juicebox" toggle in Kula — there isn't one. The whole setup starts on Juicebox's side:

1. In Juicebox, go to Integrations → Kula and choose Connect.

2. Leave that connection window open — you'll need to paste something into it once you're back from Kula.

3. Switch to Kula to generate the API key (next section).

4. Paste the key into the still-open Juicebox connection window to finish.

Generating the API key in Kula

1. Go to Settings → API management.

2. Click Create API key.

3. Under API key name, name it something recognizable, e.g. "Juicebox."

4. Under Type, select Application API. (Type can't be changed after the key is created, so get this right the first time.)

5. Under Permissions, choose Custom and select the scopes Juicebox's connection window asks for — or Full access, if that's what you intend to grant.

6. Click Generate API key, then Copy to clipboard.

7. Go back to the still-open Juicebox connection window and paste the key in to complete the connection.

Good to know

• Kula's side ends at the key. Once the key is generated and pasted into Juicebox, everything else — the connection window itself, the sync, and anything that looks wrong inside Juicebox's own UI — is Juicebox's to troubleshoot, via support@juicebox.ai. If a customer's issue is about creating, viewing, or revoking the key itself, that's Kula's side.

• An account can have at most 5 API keys at a time. If a customer's already at the limit, they'll need to delete an unused key before they can create one for Juicebox.

• The key's Type can't be changed after creation. If a Juicebox key gets created as the wrong type, the fix is deleting it and creating a new one as Application API — not editing the existing one.

• The exact scopes to select aren't prescribed by Kula — Juicebox's own connection window shows what access it's asking for; select accordingly (or grant Full access) when creating the key.

• If Juicebox reports the connection failing validation, Juicebox's own setup guidance points first at three things: the pasted credentials, the account/region, and the permission list on the key — worth checking those before escalating.

FAQ

• How do I connect Juicebox to Kula?

  Start in Juicebox: Integrations → Kula → Connect, and leave that window open. Then in Kula, go to Settings → API management, create a key named "Juicebox," set its type to Application API, choose the scopes Juicebox is asking for, generate the key, and paste it back into the still-open Juicebox window.

• Who do I contact if jobs or candidates aren't syncing correctly between Juicebox and Kula?

  Once the API key is created and connected, the sync itself is Juicebox's integration to support — reach out to support@juicebox.ai. Kula's side is limited to the API key: creating it, checking its permissions, or revoking and reissuing it if needed.

Need help?

If you have questions about your Kula API key, reach out to us at support@kula.ai or use the in-app chat. For anything inside Juicebox itself — the connection window, sync behavior, or search — contact support@juicebox.ai.