Get SRT subtitles for synthesized audio

Fetch the corresponding SRT subtitle text by audio ID. Content exists only when the srt parameter was enabled at synthesis time
(flash and instruct_mode paths do not produce SRT).

Independent auth (Bearer JWT is not used)

Identical to GET /api/tts/stream/{id}: this endpoint is JWT-exempt (app.js:263),
and instead uses query parameter auth carrying a 32-character static token, Redis key auth:user:{token}, TTL 7 days.
After the token resolves to a userId, audio ownership is still checked; mismatch returns AUTH_FORBIDDEN.

Response shape (note)

Has subtitles: Content-Type: text/plain, the body is raw SRT text, not JSON

No subtitles (upstream produced none, or the content is empty): HTTP status is still 200,
but the body is JSON {"status": 204}. Judge presence of subtitles by body shape, not by HTTP status alone

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 ********************

Responses

🟢200成功

text/plain

SRT 字幕文本；字幕不存在时改为返回 JSON {"status": 204}，HTTP 状态码依然是 200

Headers

Example

1
00:00:00,000 --> 00:00:02,150
欢迎使用 Reecho 语音合成。

2
00:00:02,150 --> 00:00:04,720
这是第二句字幕。

🟠401没有权限

🟠403禁止访问

🟠404记录不存在

🟠429

🔴500服务器错误

Get SRT subtitles for synthesized audio

Independent auth (Bearer JWT is not used)#

Response shape (note)#

Request

Request Code Samples

Responses

Independent auth (Bearer JWT is not used)

Response shape (note)