Skip to main content
POST
/
asset
/
real-human
/
sessions
Start a real-human verification session
curl --request POST \
  --url https://api.orcarouter.ai/v1/asset/real-human/sessions \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "return_url": "https://your-app.com/verify/done"
}
'
{
  "session_id": "Xa9f...40-char-token",
  "h5_link": "https://verify.example.com/?session=...",
  "status": "pending"
}

Authorizations

​
Authorization
string
header
required

OrcaRouter API keys look like sk-orca-.... Pass them in the Authorization: Bearer sk-orca-... header.

Body

application/json

Any field other than return_url is forwarded as-is to the upstream verification call, so you can pass any parameter the asset service supports. CallbackURL and ProjectName are set by OrcaRouter and cannot be overridden.

​
return_url
string

Optional http(s) URL the end user's browser is redirected to after verification, with ?status=&session_id=&group_id=. Omit to show a built-in completion page.

Response

200 - application/json

Session created

​
session_id
string
​
h5_link
string
​
status
string