Check voice-character identity-verification result

Poll the identity-verification result. Passing verification has a side effect: the voice status is advanced to lora-pending and professional-cloning training is started immediately
(modules/voiceFactory.js:1231-1235). This endpoint is therefore not a pure query and should not be blindly replayed by retry frameworks.

Three terminal states (routes/voice/verify.js:83-116):

Case	Response
Verification passed	200, top-level `passed: true`, training has started
User cancelled	200, top-level `cancelled: true`, training has not started
Not yet finished	403 `VERIFY_NOT_COMPLETED`, polling may continue

Note that "cancelled" is also 200 — the client must inspect the passed / cancelled fields and must not look at HTTP status alone.
Both fields are top-level, not under data, and appear mutually exclusively (only one of them).

A missing verification session (never started / expired) returns 404 VERIFY_SESSION_NOT_FOUND.
When the voice status is not lora-awaiting, 404 VOICE_NOT_FOUND is returned.

Legacy alias: /api/tts/voice/{id}/checkVerify — still supported for backward compatibility; use the primary path for new integrations.

Error responses take the shape { status, code, message, requestId? }. code is always the parent code — sub codes only change message and never appear in the body. requestId is present only on reportable-tier errors, so use the X-Vocu-App-Request-Id response header when troubleshooting (it is written unconditionally on every response). See the "Errors" document for the full code reference.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

application/json

查询成功。passed 与 cancelled 互斥出现，均为顶层字段

Bodyapplication/json

Example

{
    "status": 200,
    "passed": true
}

Check voice-character identity-verification result

Request

Request Code Samples

Responses