Developer / admin view

Integration console

Everything Valyd and ODIN engineers need to stand this up: the project setup, the login code, the credential data contract, the bulk onboarding of the existing ODIN workforce, and the monitoring webhooks. Each step shows the real call.

OAuth client credentials

VALYD_CLIENT_ID / VALYD_CLIENT_SECRET missing

Verification API key

VALYD_API_KEY — enables live face-scan proofs

Workflow ID

VALYD_WORKFLOW_ID — composed in the Developer Portal

Webhook signing secret

VALYD_WEBHOOK_SECRET — verifies inbound events

Create the project at dev.valyd.id

Valyd client credentials can only be issued by a human in the Developer Portal — there is no API for creating them. One visit sets up everything below.

Project name: ODIN ID
Allowed web origins: https://id.useodin.com
Redirect URL (exact, no trailing slash): https://id.useodin.com/auth/valyd/callback
Allowed scopes: profile, verifications

The client secret is shown once

Copy it immediately, along with the Verification API key on the project's Verification tab, and store both server-side only.

Server environment

.env (server only)

VALYD_CLIENT_ID=9357c59bc1794b4c9efe8823e5878147
VALYD_CLIENT_SECRET=sk_live_...
VALYD_API_KEY=vrf_...
VALYD_WORKFLOW_ID=wf_...
VALYD_WEBHOOK_SECRET=whsec_...
# optional: force the exact registered callback
VALYD_REDIRECT_URI=https://id.useodin.com/auth/valyd/callback

Secrets are read inside request handlers, never at module scope, and never shipped to the browser.