Skip to content
Niu DocsNiu 牛元文档
Dashboard控制台

Create upstream human verification session

Generated from the checked-in source. Do not edit this reference by hand.

POST /v1/media/verifications

Current workspace API key, model grant, composed workspace/key model and Provider policy, eligible published route and selectable credential required. Original immutable account/model binding is revalidated; original key identity binds encryption only, not workspace access control. Only configured fastrouter-actions-v1 channels are supported. Forwards only caller-supplied optional subject_name and return_url to the upstream H5 service. Exactly one creation follows a durable claim. All after-send failures remain unknown without automatic retry. A created session is not human completion or a local liveness approval. Token and H5 URL are encrypted and absent from ordinary metadata and logs.

Operation: createMediaVerificationSession.

Use the credential and permission scope described above. Each object below is an alternative; schemes within one object are required together.

JSON
[
{
"bearerAuth": []
},
{
"niuApiKeyAuth": []
}
]

Set NIU_ORIGIN to your installation origin (without /v1). Replace path, query and header placeholders with the required values. Query examples use curl 7.87 or newer to encode values with --url-query. Use the credential scope described above; a bearer token must have the authority required by this operation.

Authentication alternative: bearerAuth.

Shell
curl --fail-with-body -X POST "$NIU_ORIGIN/v1/media/verifications" \
-H "Authorization: Bearer $NIU_BEARER_TOKEN" \
-H 'Content-Type: application/json' \
--data @request.json

Authentication alternative: niuApiKeyAuth.

Shell
curl --fail-with-body -X POST "$NIU_ORIGIN/v1/media/verifications" \
-H "X-Niu-API-Key: $NIU_API_KEY" \
-H 'Content-Type: application/json' \
--data @request.json

Location: header. Optional. Canonical nonnil UUID; unchanged replay reads saved session without repeating creation.

JSON
{
"type": "string",
"format": "uuid"
}

Required.

JSON
{
"type": "object",
"additionalProperties": false,
"required": [
"model"
],
"properties": {
"model": {
"type": "string"
},
"subject_name": {
"type": "string",
"minLength": 1,
"maxLength": 32
},
"return_url": {
"type": "string",
"format": "uri",
"maxLength": 8192
}
}
}

Saved session accepted

Content type: application/json.

JSON
{
"type": "object",
"required": [
"data"
],
"properties": {
"data": {
"type": "object",
"additionalProperties": false,
"required": [
"id",
"model",
"subject_name",
"status",
"group_id",
"expires_at",
"created_at_ms",
"updated_at_ms"
],
"properties": {
"id": {
"type": "string",
"format": "uuid"
},
"model": {
"type": "string"
},
"subject_name": {
"type": [
"string",
"null"
]
},
"status": {
"type": "string",
"enum": [
"prepared",
"unknown",
"not_sent",
"waiting_user",
"processing",
"verified",
"failed",
"expired"
]
},
"group_id": {
"type": [
"string",
"null"
],
"format": "uuid"
},
"expires_at": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"created_at_ms": {
"type": "integer",
"format": "int64"
},
"updated_at_ms": {
"type": "integer",
"format": "int64"
}
}
}
}
}

Invalid fields or query

Missing, revoked or expired API key

Workspace/key policy refusal

Owned session or model not found

Changed input, stale route, expiry, unavailable token or capacity conflict

Body exceeds bounded size

Selected channel does not configure verification management

Credential, encrypted content or bounded storage unavailable

Current workspace API key, model grant, composed workspace/key model and Provider policy, eligible published route and selectable credential required. Original immutable account/model binding is revalidated; original key identity binds encryption only, not workspace access control. Only configured fastrouter-actions-v1 channels are supported. Forwards only caller-supplied optional subject_name and return_url to the upstream H5 service. Exactly one creation follows a durable claim. All after-send failures remain unknown without automatic retry. A created session is not human completion or a local liveness approval. Token and H5 URL are encrypted and absent from ordinary metadata and logs.

Supported scope: implemented