Embedded WebSDK
Keep applicants on your website. Create an embedded session, mint a short-lived SDK token from your backend, and run Sumsubβs WebSDK in your page. Hosted invitation links (POST /api/v1/biometric/invite) stay unchanged.
Integration flow
1) POST /api/v1/biometric/embedded/sessions β reference. 2) POST /api/v1/biometric/embedded/{reference}/sdk-token β access_token (Bearer, backend only). 3) Initialize Sumsub WebSDK on your page with that token. 4) Poll GET /api/v1/biometric/{reference}. Do not use the public hosted start endpoint for embedded sessions, and never put Peleza client secrets in the browser.
- Separate from hosted invite β no invitation_url and no redirect to verify.peleza.com.
- Mint token: POST /api/v1/biometric/embedded/{reference}/sdk-token (same Bearer auth as other private routes).
- Result polling reuses GET /api/v1/biometric/{reference}; billing uses the same biometric pricing as hosted invites.
Create embedded session
{{baseUrl}}/api/v1/biometric/embedded/sessionsHeader
Body Parameters
Request payload
All verification APIs require consent: true in the JSON body.
{
"email": "john.doe@example.com",
"first_name": "JOHN DOE",
"last_name": "JOHN DOE",
"message": "sample-value",
"consent": true
}Expected response
{
"success": true,
"response_code": 200,
"message": "Embedded verification session created for jane@peleza.com.",
"data": {
"verification": {
"name": "Jane Doe",
"first_name": "Jane",
"last_name": "Doe",
"email": "jane@peleza.com",
"reference": "a1b2c3d4-e5f6-4789-a012-3456789abcde",
"delivery": "embedded",
"expires_at": "Oct 21, 2026 15:04"
}
},
"request_id": "550e8400-e29b-41d4-a716-446655440000"
}Response Fields
Set {{baseUrl}} to https://api.peleza.com (production) or https://sandbox.peleza.com (sandbox). Authenticated calls need a Bearer token from POST /api/v1/oauth/token.
