Ashby — a recruiting platform (applicant tracking system, ATS) — helps companies manage hiring, from application and interviews through offer and hire.

The Sumsub and Ashby integration adds identity verification to your hiring process. When a candidate application reaches an interview plan stage you choose (for example, Offer), Sumsub creates a verification link on the candidate Ashby profile. Once the candidate completes the check, the verification result and verified identity data are written back to the same profile.

Your recruiting team does not need to request ID documents by email or copy results from a separate tool. Recruiters stay in Ashby, the verification result sits alongside the rest of the candidate information, and you control exactly when in the hiring process the check happens.

Example use cases

The Ashby integration supports the following common use cases.

Key features and benefits

Key features and benefits of the Ashby integration include the following:

• Verification without leaving Ashby. The verification link is created, and the result is written back automatically, on the candidate profile recruiters already work from. The verification status, verified first name, last name, and date of birth are stored in dedicated Sumsub fields on the candidate Ashby profile.
• Control over timing. Choose the Ashby interview plan stage that triggers verification, for example, Offer, so the check does not add friction earlier in your hiring process.
• Flexible verification settings. Use the verification levels you already configure in your Sumsub account. Select a default level, override it for specific candidates, and set how long a verification link stays valid, from 30 seconds to 30 days (7 days by default).
• Automatic name cross-check. The integration compares the name on the verified identity document with the name on the candidate Ashby profile and flags a mismatch for the recruiter to review.
• No development. Enabling the integration automatically creates the required custom fields and webhook in your Ashby workspace. The only manual step is creating an Ashby API key.
• Human-in-the-loop decisions. Verification results support recruiter decision-making, but candidates are never automatically approved or rejected in Ashby. Recruiters retain full control over the final decision.

How Ashby integration works

The Sumsub and Ashby integration adds identity verification to your hiring process. You decide at which interview plan stage the check starts, and Sumsub creates the verification link and writes the result back to the candidate's Ashby profile. The verification workflow operates as follows:

1. A recruiter moves a candidate application to the trigger stage you configured.
2. Within seconds, Sumsub creates an applicant for the candidate (or reuses an existing one) and adds a verification link, a Pending status, and a note to the candidate's Ashby profile.
3. The recruiter copies the link and shares it with the candidate through their usual channel, such as email or a messenger.
4. The candidate completes verification on the Sumsub-hosted verification page.
5. Once the review is completed, the verification result and verified identity data are written back to the candidate profile, usually within one to three minutes and no later than six minutes.
6. The recruiter reviews the result and decides on the candidate application.

Get started with Ashby integration

To get started with the integration, contact your Customer Success Manager at [email protected]. They will enable the integration for your account.

You also need:

• An Ashby workspace where you can create API keys.
• At least one individual verification level configured in Sumsub. To create a new level, refer to this article.

Once the integration is enabled for your account, follow the steps below.

Step 1: Create Ashby API key

First, create an API key in Ashby that allows Sumsub to read candidate profiles, write verification results, and set up the integration in your workspace. To do so:

1. In Ashby, navigate to Admin → Integrations → API Keys and create a new key.

2. Grant the key the following permissions:

   Permission	Purpose
   candidatesRead	Read candidate profiles, including the name used for the name cross-check.
   candidatesWrite	Write verification results to candidate fields and notes.
   hiringProcessMetadataRead	Look up the Sumsub custom field definitions.
   hiringProcessMetadataWrite	Create the Sumsub custom fields when you enable the integration.
   apiKeysWrite	Create and remove the stage-change webhook.

3. Copy the key. You will need it in the next step.

Step 2: Enable integration in Sumsub

Connect your Ashby workspace to Sumsub and configure when and how candidates are verified. To do so:

1. In the Marketplace, open the Ashby card.

2. Fill in the following fields:

   Field	Description
   Ashby API key	The key you created in Step 1.
   Trigger stage name	The Ashby interview plan stage that starts verification, for example, Offer.
   Verification level	The default Sumsub verification level for candidates. You can override it for a specific candidate in Ashby.
   Link lifetime	How long a verification link stays valid. The default is 7 days. The allowed range is from 30 seconds to 30 days.

3. Click Enable.

Once enabled, the integration automatically creates the Sumsub custom fields on the Candidate object and a stage-change webhook in your Ashby workspace. You do not need to set up webhooks or fields in Ashby manually.

Sumsub fields in Ashby

The integration stores verification data in the following custom fields on the Ashby Candidate object.

Edit integration settings

You can change the integration settings at any time without re-enabling the integration.

1. In the Dashboard, navigate to Marketplace and open the Ashby card.
2. Update the fields you need: Ashby API key, Trigger stage name, Verification level, or Link lifetime.
3. Save the changes.

The changes take effect within minutes.

Disable integration

To disable the integration:

1. In the Dashboard, navigate to Marketplace and open the Ashby card.
2. Disable the integration.

Sumsub removes the stage-change webhook from your Ashby workspace, so moving candidates to the trigger stage no longer starts verification. The Sumsub custom fields and their values remain on candidate profiles, as the Ashby API does not allow deleting or archiving custom fields.

To hide the Sumsub fields from candidate profiles:

1. In Ashby, navigate to Admin → Organization Setup.
2. Open the Candidate tab.
3. Find a Sumsub field, for example, Sumsub verification link, and archive it.
4. Repeat the previous step for each of the eight fields listed in Sumsub fields in Ashby.