Get help Launch Nametag

Get started

Interactive validation Browser SDK Avoid storing PII API reference Request states & events MCP server Nametag webhooks

Account recovery

Self-service recovery — admin Self-service recovery — end user Autopilot account binding Birth date hashes

Integrations

Breezy HR Auth0 Workable ServiceNow Slack Raw webhook data to Slack Workday Greenhouse Tines Cloudflare CyberArk Jira Service Management integration Zoom Entra ID Okta Cisco Duo OneLogin Authentik Apereo CAS Ashby Beyond Identity Clerk CyberArk Workforce Identity Dover Gusto Zendesk Intercom Lever Freshdesk Recruitee JOIN Stytch Slate by Technolutions TalentLyft WorkOS CATS Active Directory Polymer Docusign integration addBuild your own integration

SSO & identity

SAML SSO with Entra ID SAML SSO with Okta Okta API Services Okta Custom IDV Okta EAM Entra ID EAM

SCIM

Overview Okta

Directory agents

Directory agent Directory agent protocol Directory agent: Okta LDAP

Logging & data

Logging to CrowdStrike Logging to Splunk Logging to Sentinel Enterprise Data Custody GPS location IP address ranges addStream to your own tools

Reference

Document types Self-service parameters CLI Changelog Fraud investigation MCP tool reference

Integrations chevron_right Slate by Technolutions

Nametag Integration for Slate

Verify applicant identity with Deepfake Defense during Slate admissions and write a pass/fail signal back onto the Slate record.

Sign in required

This part of the documentation is private and requires you to sign in to view it.

Have an access code instead? Enter it here:

← Previous

Stytch

TalentLyft

On this page

Overview How it works Before you start Step 1 — Connect to Slate Step 2 — Choose who it covers Step 3 — Set when it runs, and import the Slate blueprint Step 4 — Review and activate What your Slate rules do with the result Managing the connection Troubleshooting

search ESC

↵ to open esc to close