One workflow ID.
Fresh sessions.
A small REST surface for credential-backed identity, age verification, document signing, and concise attestations. Test identity and age with the EUDI reference wallet; production routes require provider, issuer, and Alentra acceptance.
The real request shape
① Create a session
curl https://api.alentra.app/v1/sessions \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Idempotency-Key: order_o456" \
-F 'workflow_id=wf_customer_onboarding' \
-F 'metadata={"case_id":"case_4815"}' \
-F '[email protected];type=application/pdf'
Response:
{
"id": "sess_abc123",
"workflow_id": "wf_customer_onboarding",
"workflow_revision": 3,
"url": "https://alentra.app/s/sess_abc123",
"status": "created",
"expires": "2026-04-26T12:34:56Z"
}② Receive a signed webhook on every step
POST https://your-app.com/alentra-webhook
X-Alentra-Event: step.completed
X-Alentra-Timestamp: 1785088800
X-Alentra-Signature: <hmac-sha256 of timestamp.body>
X-Alentra-Delivery-Id: sess_abc123:step.completed:0
{
"event": "step.completed",
"delivery_id": "sess_abc123:step.completed:0",
"data": {
"session_id": "sess_abc123",
"stage": 0,
"primitive": "identify",
"audit_id": "sess_abc123_0",
"claims": { "first_name": "Jane", "country": "US" }
}
}Four steps from sandbox
Publish the workflow
Arrange the primitives once, choose API-only access, configure delivery, and publish a fixed revision.
Create a fresh run
Send the workflow id plus optional metadata and files, then hand the user the returned hosted URL.
Receive the result
Get a signed webhook on every step — the verified claims and signatures land as they happen, in order.
Request production access
Complete the applicable provider and issuer approvals, configure production trust, and pass each route acceptance review.
Explore the APIs.
Identify
↗Government-attested identity from the user's wallet — name, DOB, country, doc status.
Age Verify
↗The business receives only true/false for the threshold; Alentra processes DOB and retains encrypted signer evidence.
Sign
↗Upload exact documents for Alentra to hash, present, and retain with immutable completed evidence.
Attestation
↗Capture attested approval of concise inline terms of up to 1,000 words.
Which wallets do what.
Runtime capability data is read from the API. Sandbox and production are shown separately; availability still depends on browser support, provider approval, and the user's credential.
| Credential route | Sandbox | Production | Identify | Age verify | Attestation | Sign |
|---|
Adapter support is read from the API. Production availability also requires provider approval, credentials, and a compatible user environment.
Start in the sandbox.
Create an account, configure signed webhooks, and test the exact session flow before requesting production access.