Skip to main content

About the integration

Juicebox’s integration with Eploy allows you to:
  1. Export Profiles to Eploy: Save profiles directly into Eploy, including contact details, current company and job, profile URLs, and more.
    1. [Configurable] Auto-Export: Juicebox has the ability to auto-export profiles to your ATS with configurable triggers, including after shortlisting, after adding to a sequence, or after an interested response.
  2. Link Eploy Jobs to Juicebox
    1. Import Job Descriptions: Import a job description from Eploy into Juicebox to automatically kick off a search using the job description.
    2. Simplify Exports: When exporting a profile from Juicebox to the ATS, it will automatically be connected to the correct job in the ATS. More details here.
  3. View Profiles in Eploy: View profiles already in Eploy within Juicebox. Avoid reaching out to the same profile twice, and instantly view your relationship history.

Start a project via the Eploy integration

Open the projects page and select Import Job from ATS / CRM. You will then see your Eploy jobs and can select the corresponding option.

Export profiles to Eploy

Follow the regular export steps and select Export to Eploy on either an individual profile or a bulk export. After exporting, you will see the profile created in your Eploy account.

View profiles already in Eploy

Juicebox will tag profiles that already exist in Eploy. You will see the last modified date, as well as the option to view the profile directly in Eploy by clicking the View in ATS button.

Set up an API user

To allow access to the Eploy API, you need to create a special user account that has access to the API.
  1. In Eploy, go to Admin > Users. Here you see all users you can manage.
    Users page under Admin in Eploy
  2. Click New > User to create a new standard user.
    Creating a new user in Eploy
  3. On the form, complete the following fields:
    • User Display Name: Use a unique name that describes the user, for example “API User”.
    • User Name: Use a unique name for your API user.
    • Roles: Assign exactly one role to the user. Only one role may be assigned to an API user, and the role’s permissions determine which fields and data the API can access.
    • System Email Address, Email Display Name, and Your Direct / Internal Email Address: Use a generic email address that is not used by any real users, for example noreply@yourcompany.com.
Before saving the user, set up IP restrictions as described in the next section.

Assign IP restrictions

For the user to be able to access the API, specify at least one IP range in the Restricted IP Access section.
  1. Click the Add button in the Restricted IP Access section.
    Add button in the Restricted IP Access section
  2. Enter 0.0.0.0/0 and click Save to allow access from any IPv4 source.
    Entering the IPv4 range
  3. Click Add a second time, enter ::/0 to allow access from any IPv6 source, then click Save.
    Entering the IPv6 range
    Both IP ranges added to Restricted IP Access
  4. Click Save at the bottom of the page to create the API user.

Find your subdomain

The subdomain is the first part of the URL you use to log in to your Eploy account, the word right before .eploy.net. For example, if your login URL is https://acme.eploy.net, your subdomain is “acme”.
Finding the subdomain in the Eploy login URL
Enter the subdomain in the connection pop-up and click Continue.
Entering the subdomain in the connection flow

Create an API key

  1. In Eploy, go to Admin > Security Settings > API Keys.
    API Keys section under Security Settings
  2. In the API Keys section, click the New > REST API menu link.
    New REST API menu link
  3. On the Create API Key page, enter a name for your API key, select the user you created earlier, and click Save.
    Creating the API key and selecting the API user

Add API permissions

The connection pop-up lists the permissions the integration needs.
Permission list shown in the connection flow
For each permission, repeat the following process:
  1. Click the Add button under API Permissions.
    Add button under API Permissions
  2. Select a permission type in the API dialog.
    Selecting a permission type in the API dialog
  3. Check the permission boxes as required, then save.
    Checking the permission boxes
After all the permissions have been added, double-check that they match what is listed in the connection pop-up.
Reviewing all added permissions
Click the save button to save the API key.
Saving the API key

Get the Client ID and Client Secret

  1. Click the Generate New Client ID & Secret button.
    Generate New Client ID and Secret button
  2. In the dialog that appears, click the Show link and copy the Client ID and Client Secret values.
    Dialog showing the Client ID and Client Secret
    Copying the Client ID and Client Secret into the connection flow

Setting up the integration

  1. Navigate to the Integrations tab on the Juicebox platform.
  2. Select Eploy and click Activate. You can also use the search bar at the top.
  3. Follow the instructions in the connection pop-up, entering your subdomain, Client ID, and Client Secret when prompted, then click Set up integration.
  4. After you have clicked through the remaining pages of the pop-up, the configuration will be completed. If successful, you will see a green Connected button in your Integrations marketplace.
Congratulations! You have successfully integrated Eploy and Juicebox.
If you receive an error about missing permissions despite configuring your key correctly, the user who owns the key likely does not have the appropriate permissions. The user owning the key must have at least the same permissions as the key.
It may take a few minutes for all data to sync between Juicebox and Eploy.

Support

For an overview of all integration features, see ATS Integrations. If you’re facing any issues with your integration, contact our support team at support@juicebox.ai.