Docs Index

Lever (Legacy integration guide)

Last updated on Available in French

Note: Lever Live Pad integration requires a Professional or Enterprise Lever plan and a CoderPad paid organization plan (Team or higher). To configure the integration, you must be a Lever Super Admin and CoderPad organization Admin. If you’re on a CoderPad Personal plan, please consider upgrading to access this feature.

CoderPad integrates with the Lever applicant tracking system to automatically create CoderPad interview sessions for candidates. Apply the "coderpad" tag to jobs or candidates in Lever to automatically create pads.

When a tagged candidate reaches the first designated Lever stage (see Step 2 below), CoderPad creates a pad and updates the Lever candidate profile with the interview link:

Lever candidate page with coderpad live pad link highlighted on the right.

You then copy this link and send it to the candidate (and interviewer).

To enable the integration, you’ll need to provide CoderPad with Lever API credentials, and provide Lever with a CoderPad webhook URL.

Step 1: Provide CoderPad with Lever credentials

To get started, visit the CoderPad Lever integration page

Lever configuration page on coderpad site. Fields for Lever API key, lever webhook signature token, and "who should own pads created through his integration" are displayed.

You need two pieces of information from Lever: an API key and a Webhook signing token. The API key is needed so we can fetch candidate information from Lever and update the candidate profile with the pad link. The Webhook signing token verifies web requests sent from Lever.

Generate a Lever API key

To continue, you must be a Lever Super Admin and your organization must be on a Professional or Enterprise Lever plan.

Go to Lever and navigate to Settings: Integrations and API.

Under the heading Lever API credentials, click the blue Generate New Key button. For the integration name fill in “CoderPad”.

Copy the new API key to your clipboard. You will need it later and won’t be able to view it other than at this time.

Grant these permissions by checking the corresponding check boxes:

  • Read: Read stage
  • Read: Read opportunity
  • Read: List stages
  • Write: Add opportunity link

Click the blue Done button then confirm that you Got it to persist the key in Lever.

A pop up window on the permissions page that says "this is the one and only time that this api key will be accessible. are you sure you would like to proceed? you can generate or revoke api credentials for this integration at any time."

Return to CoderPad and paste the API key that you copied into the text box Lever API key.

Get webhook signing token

Lever signs requests using a webhook signing token. CoderPad uses this token to verify that the requests came from Lever. 

Back in Lever, navigate to Settings: Integrations and API: Webhooks tab. Look for the section Candidate Stage Change. Click + Add Webhook

The "signature token" field is highlighted.

Copy the Signature Token and return to CoderPad and paste it into the text box Lever Webhook signature token.

Choose a pad owner

Please choose the CoderPad user from your organization who will own the Pads created by this integration. Typically this is a recruiter or an account like [email protected]

Save and test

The page should now look like this:

Lever configuration page on coderpad site. Fields for Lever API key, lever webhook signature token, and "who should own pads created through his integration" are displayed.

Press Save, and we’ll test and persist your credentials. If it worked it’ll look like this:

Integrations page with a banner at the top that says "changes have been saved and the lever api key has been tested successfully".

If unsuccessful, make sure you pressed Done in Lever after creating the API key. Also try creating a new key again, ensuring it has the correct permissions.

After you’ve added the Signature Token to CoderPad, choose the candidate stages to create pads, then connect to the new webhook in Lever.

Step 2: Choose candidate stages

Please choose the Lever candidate stages for creating pads. For example, “Phone Screen” or “On-site”. You can choose multiple stages – but a coderpad will only be created in the first designated stage that a candidate is moved into. Press Save.

"Step 2: Select lever candidate stage" page with the "phone screen" option selected.

Step 3: Provide Lever with a CoderPad webhook URL

Your Lever integration page now shows a webhook URL at the bottom:

The "step 3: add your webhook url into lever" page with the candidate stage change url highlighted.

Copy this URL to your clipboard.

Go back to the Lever Settings: Integrations and API: Webhooks tab. Under the heading Webhooks, go back to the Candidate state change section. 

First, toggle its switch to on/green. 

Then, use the down arrow to expand the details of the webhook you created in Step 1 of this guide. Paste your copied candidate state change URL into the webhook title to replace the placeholder URL https://yoursite.com

 Press Verify Connection. It should spin, then show Verified.

The candidate state change url is highlighted and the verify connection button is highlighted.

The integration setup is now complete. Next, select specific jobs or candidates to create pads for.

Using the integration

Enable integration for specific jobs or candidates

Enable for a job

If you tag a job in Lever with “coderpad”, CoderPad checks for candidates who’ve applied to this job. When a candidate for this job enters the first “CoderPad designated” stage (selected in Step 2 of setup), CoderPad creates a pad link for them.

"Step 2: Select lever candidate stage" page with the "phone screen" option selected.

To enable this, view a job in Lever and apply the “coderpad” tag:

Job posting page with the "coderpad" tag highlighted at the bottom right corner of the page.

To disable this, remove the “coderpad” tag from the job.

Enable for a candidate

You can also tag a specific candidate with “coderpad”. When this candidate enters the first “CoderPad designated” stage, CoderPad creates a pad link for them.

The Lever overview page with the coderpad tag highlighted at the bottom of the page.

Disable for a candidate

Do you have a candidate who applied to a coderpad-tagged job, for whom you don’t want a pad created? You can disable CoderPad for these candidates by viewing their Lever candidate profile and removing the “coderpad” tag. When the candidate enters a designated stage, CoderPad will not create a pad for them.

Schedule a CoderPad phone screen

At this point, you’ve integrated Lever and CoderPad and tagged specific jobs or candidates with “coderpad”.

To trigger the integration, move a matching candidate through your interview flow. At the first stage that was “CoderPad designated”, CoderPad creates a pad and adds the link to the Lever candidate profile:

Candidate page with the applied job and candidate status highlighted in the center of the page. The pad link is highlighted on the right side of the page.

Please note this consumes pad quota!

Ensure that you only move “coderpad” tagged candidates into “CoderPad designated” stages when you want to create a pad for them. Remember, you can disable this for a single candidate by removing their “coderpad” tag.

Finally, copy the CoderPad link. When you schedule the interview, include the link in the invitation:

The schedule page is shown on lever with an invitation to the pad displayed and the pad link is highlighted.

You’re done!

View results

When the CoderPad interview ends, you may wish to view the results in Lever. The same CoderPad link we added to the candidate page also serves as a record of the interview. Click that link to play back the history of the interview session. You can also copy code from the interview into a candidate note or feedback.