Start voice-character identity verification
POST
https://v1.vocu.studio/api/voice/{id}/startVerify
lora-awaiting (waiting to queue for professional cloning) and return a redirect URL for the user to complete face verification.url field, not under data (routes/voice/verify.js:49-52).status = lora-awaiting can start verification; any other status is always 404 VOICE_NOT_FOUND(the query in
modules/voiceFactory.js:1225-1229 hard-codes the status in the where clause, so a status mismatch cannot be distinguished from a missing voice).VERIFY_CERT_INVALID immediately and the upstream is not called.When the upstream reports a name/ID mismatch, 403
VERIFY_CERT_MISMATCH is returned; other upstream failures uniformly return 500 VERIFY_START_FAILED.url, guide the user to complete verification on that page, then poll the "check identity-verification status" endpoint for the result.Legacy alias: /api/tts/voice/{id}/startVerify— still supported for backward compatibility; use the primary path for new integrations.
{ 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.Request
Path Params
Request Code Samples
Responses
Modified at 2026-08-23 01:11:55