Skip to Content
VerifyCreate a workflow

Create a workflow

🔑 What you leave with: an App API key (shown once), a workflowId, and a webhook secret

Portal setup for Reusable Verification: where verification lives in the Developer Portal , and the three things to grab before your first session. Don’t have an account yet? Create one first — it takes a minute and comes with a $100 welcome credit.

Where verification lives in the portal

Verification is configured inside your app — the same app whose OIDC credentials power Connect with Valyd. Open the project → Workflows in the sidebar:

The Workflows page of a project in the Developer Portal

(Building only with the Unique Human API? No project needed — every organization has a built-in Unique Human API key on the dashboard for no-account anti-spoof checks; see that page’s setup section.)

Get your API key (shown once)

When you rotate the key on the app’s API keys page, the portal shows the API key exactly once in a show-once panel. Copy it immediately and store it server-side — it cannot be retrieved again. If you lose it, rotate it in the portal to mint a new one.

Never put the key in browser code: it belongs in your backend’s environment, passed to the SDK client on server-to-server calls only.

Build the workflow

A workflow is the saved bundle of checks your app requires — KYC, professional license, face match, liveness, location, and more. Build one with the workflow wizard and copy its workflowId:

The workflow creation wizard in the Developer Portal

Set the Return URL

While creating or editing the workflow, set its Return URL — the page the user lands on after they finish (or abandon) the check. A few rules:

  • It must be an https:// address on your own site.
  • Leave it empty to keep the user on Valyd after the check.
  • The Return URL is a trusted workflow setting. Valyd never accepts a return address per verification session, so a session can’t be pointed at an attacker-controlled URL (open-redirect protection).

Valyd appends ?session_id=…&status=… when it sends the user back, but treat that status as a hint only — confirm every result with the decision endpoint or the signed webhook.

Configure webhooks

Set your endpoint URL and copy the signing secret under Webhooks. Valyd POSTs signed events there when a session finishes — Webhooks covers verification of the signature. The portal includes a webhook tester so you can fire test events at your endpoint before going live:

The webhook tester in the Developer Portal

Next

Last updated on