Nametag Integration for Ashby

Overview

The Nametag and Ashby integration enables organizations to verify candidate identities directly in their hiring workflow. By connecting Nametag to Ashby, recruiters can confirm that candidates are who they claim to be — using a government-issued ID and a live selfie — at key points in the pipeline, and have the results written back to the candidate automatically.

Unlike some integrations, Ashby connects with a single per-workspace API key (not an OAuth flow). The verification checks are triggered by Ashby webhook events (for example, when an interview is scheduled or an offer is created), and results are written back to the candidate as custom fields, tags, a note, and — optionally — a verification certificate.

Prerequisites

Before setting up the integration, ensure you have:

1. An active Nametag account with the Ashby integration enabled for your environment.
2. Admin permissions in Ashby (required to create an API key).

Setup

Setup has two parts: create an API key in Ashby, then connect it in the Nametag Console. The Nametag setup screen walks you through both.

Step 1: Create an API key in Ashby

1. In Ashby, go to Admin → Developers → API keys.

2. Create a new API key.

3. Set the Integration Partner to Nametag.

4. Grant the key the following scopes:

   • candidatesRead
   • candidatesWrite
   • hiringProcessMetadataRead
   • hiringProcessMetadataWrite
   • interviewsRead
   • organizationRead
   • apiKeysWrite

5. Copy the generated key. You will paste it into Nametag in the next step.

Step 2: Connect Nametag to Ashby

1. In the Nametag Console, go to Configure.
2. In the left sidebar, select Integrations.
3. Select Add Integration and choose Ashby.
4. Optionally give the integration a name (visible only inside Nametag).
5. Paste the API key you created in Step 1.
6. Select Connect to Ashby.

When you connect, Nametag validates the key, then automatically provisions the resources it needs in your Ashby workspace:

• The custom fields used to store verification results on the candidate.
• The candidate tags used to label verification outcomes.
• The webhooks used to trigger checks from your pipeline.

Provisioning is idempotent — reconnecting adopts the existing fields and tags by name rather than creating duplicates.

Note: If the API key is missing any required scopes, the Nametag Console shows a warning listing the missing scopes. Regenerate the key in Ashby with all of the scopes above and reconnect.

Configuration

After connecting, you land on the integration’s detail view, where you choose when checks run and what gets written back.

Triggers

Triggers control which Ashby events launch a Nametag identity check. Enable any combination of:

By default, Interview scheduled and Offer created are enabled. When Candidate stage change is enabled, you can pick the specific stages that should launch a check.

Outputs

Outputs control what Nametag writes back to the candidate in Ashby after a check completes:

Additional settings

• Flag pending or failed checks for recruiter follow-up — applies a tag so recruiters can find candidates whose verification is pending or did not pass.
• Require location integrity — factors device/location integrity signals into the outcome.
• Write fraud status back to Ashby — after a definitive decision, calls Ashby’s candidate fraud-status API. Off by default.

Verification flow

1. A candidate progresses through the hiring pipeline in Ashby.
2. A configured event fires (for example, an interview is scheduled).
3. Ashby sends a webhook to Nametag; Nametag verifies the signature and launches an identity check for the candidate.
4. The candidate completes identity verification with Nametag (government ID + live selfie).
5. Nametag determines the outcome and writes the results back to the candidate in Ashby according to your output settings.

Data written to Ashby

Nametag stores verification information directly on the candidate in Ashby. If the required custom fields or tags do not exist, Nametag creates them during setup.

Custom fields created by Nametag

Tags and notes

• A candidate tag reflecting the verification outcome (and, if enabled, a follow-up tag for pending/failed checks).
• A note on the candidate summarizing the outcome, with a link to the full report in Nametag.

Certificate (optional)

When the Certificate output is enabled, Nametag uploads a PDF Identity Verification Certificate to the candidate’s files. The certificate summarizes the verified attributes, the verification timeline, and device/network/location context.

Permissions and scopes

The Ashby API key you create must include the scopes listed in Step 1. These allow Nametag to:

• Read candidate and application information to associate a check with the correct candidate.
• Write to candidates to store verification results (custom fields, tags, notes, files).
• Read and write hiring-process metadata to provision and populate the Nametag custom fields and tags.
• Read interviews to support interview-based triggers.
• Read organization information to validate the connection.
• Manage webhooks (apiKeysWrite) to register the event subscriptions that trigger checks.

Nametag requests only the minimum permissions required for the integration to function. No candidate PII is stored in Ashby by Nametag beyond the verification result and links — the verified identity is held by Nametag.

Removing the integration

You can disconnect the Ashby integration at any time from the Nametag Console.

1. In the Nametag Console, go to Configure.
2. In the left sidebar, select Integrations.
3. Locate the Ashby integration.
4. Select Remove.

Once disconnected:

• Nametag will no longer receive Ashby events or write results back.
• The Ashby webhooks Nametag registered are removed.
• Existing data already written to candidates in Ashby remains unchanged.

To revoke access entirely, delete the API key in Ashby (Admin → Developers → API keys).