Developer platform

DAJU Verify API v1

Create and retrieve verification sessions from server-side applications. The current API foundation supports API-key authentication, environment isolation, idempotent creation, correlation IDs, and request logging.

Quick start

1. Create a sandbox application, workflow, and API credential.
2. Keep the raw API key in a server-only secret store.
3. Send an Idempotency-Key when creating a verification session.
4. Redirect the customer to the returned one-time hosted URL.

curl -X POST https://daju-mocha.vercel.app/api/v1/verification-sessions \
  -H "Authorization: Bearer $DAJU_API_KEY" \
  -H "Idempotency-Key: onboarding-customer-123-v1" \
  -H "Content-Type: application/json" \
  -d '{
    "workflowId": "22222222-2222-4222-8222-222222222222",
    "externalReference": "customer-123",
    "hostedReturnUrl": "https://merchant.example/verification/return"
  }'

Operational rules

Keys are bound to one sandbox or live application. Public session creation is sandbox-only in this phase; live creation fails closed until production-readiness controls are enabled.
Reuse an idempotency key only for an identical creation request.
An optional hostedReturnUrl must exactly match a configured application allowlist entry. It must use HTTPS and cannot contain credentials, a query string, or a fragment.
DAJU never appends a session token, status, result, or evidence to a return URL. Use signed webhooks or the retrieval API to determine the outcome.
Record the X-Correlation-Id response header when contacting support.
Read RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset on authenticated responses. A 429 response also includes Retry-After.
Hosted URLs contain secret bearer material and are returned only when a session is created.
Webhook outcomes distinguish terminal completion or failure from retry required, inconclusive, and manual-review states. Only a signed verification.completed event is an approval.
Requests larger than 16 KiB are rejected.

OpenAPI 3.1 JSON Integration templates

Product patterns

Start from a sandbox integration.

Use copyable TypeScript patterns for RentDirect, Trellis, Student Device Leasing, and NELLA Support. Each template documents its verification purpose, assurance target, workflow checks, safe webhook events, and retention boundary.

Browse integration templates