SRT to SCC API - Convert SRT to SCC API: Pricing, Documentation
by Pixazo
SRT is the lingua franca of web subtitles, but broadcast and cable delivery specs still demand SCC. The Pixazo SRT to SCC API maps your SubRip cues into frame-accurate CEA-608 closed captions with a single POST, then hands back a request_id you poll to completion. Prefer a no-code option? The same conversion is available free in your browser as the SRT to SCC Converter.

Models Version
Get $5 Free Credit on First Payment
No strings attached — add funds and get $5 bonus instantly
SRT to SCC API Documentation
Authentication
Every request is authenticated with your Pixazo API key in the Ocp-Apim-Subscription-Key header — the same key across every Pixazo endpoint.
| Header | Required | Value |
|---|---|---|
Ocp-Apim-Subscription-Key | Yes | Your Pixazo API key |
SRT to SCC generate request
SubRip (.srt) carries plain-text cues with millisecond timing, which is perfect for HTML5 players but unusable for compliance workflows that require line-21 or CEA-608 caption data. Scenarist Closed Caption (.scc) encodes captions as timecoded hexadecimal control codes tied to a specific frame rate, the format broadcasters, MAM systems, and FCC-facing deliverables expect. The Pixazo caption-convert endpoint parses each SRT cue, quantizes its timing to your target frame rate, and emits valid SCC command bytes so the file drops straight into a broadcast pipeline. Because the source SRT is never modified, you can regenerate SCC at a different frame rate without re-authoring. The job runs asynchronously so long caption tracks never block your request.
Endpoint: POST https://gateway.pixazo.ai/media-tools/v1/caption-convert
Request Code
curl -X POST 'https://gateway.pixazo.ai/media-tools/v1/caption-convert' \
-H 'Ocp-Apim-Subscription-Key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"subtitle_url":"https://example.com/input.srt","to_format":"scc","source_format":"srt"}'Output
{
"request_id": "req_9f3c1a7b2e",
"status": "QUEUED",
"polling_url": "https://gateway.pixazo.ai/v2/requests/status/req_9f3c1a7b2e"
}Webhook (Optional)
Instead of polling, include a webhook_url in the request body and Pixazo will POST the completed job payload to that URL when the conversion finishes. The webhook body is identical to the completed-status response shown under Retrieving Results.
Request Parameters
| Parameter | Required | Type | Default | Allowed | Description |
|---|---|---|---|---|---|
subtitle_url | Required | string | — | HTTP(S) URL | URL of the source caption file. |
to_format | Required | string | — | srt, vtt, scc | Target caption format. This page documents "scc". |
source_format | Required | string | — | srt, vtt, scc, ass, ssa, sub | Format of the source file. Required — inputs are re-hosted without their extension, so it cannot be inferred. |
clean | Optional | boolean | false | true / false | Strip formatting tags and positioning from the cues. |
webhook_url | Optional | string | — | HTTP(S) URL | Receive the completed job via webhook instead of polling. |
Example Request
curl -X POST 'https://gateway.pixazo.ai/media-tools/v1/caption-convert' \
-H 'Ocp-Apim-Subscription-Key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"subtitle_url":"https://example.com/input.srt","to_format":"scc","source_format":"srt"}'Response
Every request returns a request_id immediately with a QUEUED status. Use the polling_url (or a webhook) to retrieve the finished file.
{
"request_id": "req_9f3c1a7b2e",
"status": "QUEUED",
"polling_url": "https://gateway.pixazo.ai/v2/requests/status/req_9f3c1a7b2e"
}Request Headers
| Header | Required | Value |
|---|---|---|
Ocp-Apim-Subscription-Key | Yes | Your Pixazo API key |
Content-Type | Yes | application/json |
Response Handling
The submit call returns one of the HTTP status codes below. A 202 means the job was accepted — everything else is an error you should handle.
| Code | Meaning |
|---|---|
| 202 | Accepted — the job was queued; poll the status URL. |
| 400 | Bad request — a parameter is missing or invalid. |
| 401 | Unauthorized — missing or wrong API key. |
| 402 | Payment required — insufficient balance. |
| 429 | Too many requests — you are being rate-limited. |
| 500 | Server error — transient; retry with backoff. |
Error Responses
Errors return a JSON body with a machine-readable code and a human-readable message.
{
"request_id": "req_9f3c1a7b2e",
"status": "FAILED",
"error": {
"code": "INSUFFICIENT_BALANCE",
"message": "Your account balance is too low to process this request."
}
}Retrieving Results
Poll the status endpoint until the job reaches COMPLETED (or FAILED).
curl 'https://gateway.pixazo.ai/v2/requests/status/req_9f3c1a7b2e' \
-H 'Ocp-Apim-Subscription-Key: YOUR_API_KEY'Response (Completed)
{
"request_id": "req_9f3c1a7b2e",
"status": "COMPLETED",
"model_id": "caption-convert",
"output": {
"media_url": "https://api-assets.pixazo.ai/out/result.scc",
"media_type": "SCC"
},
"error": null,
"created_at": "2026-01-01T00:00:00Z",
"completed_at": "2026-01-01T00:00:04Z"
}Response Fields
| Field | Type | Description |
|---|---|---|
request_id | string | Unique id for this job. |
status | string | One of the job status values below. |
output.media_url | string | URL of the converted file (when completed). |
output.media_type | string | Output format (SCC). |
error | object | null | Populated only when status is FAILED. |
Status Values
| Status | Meaning |
|---|---|
| QUEUED | Job accepted, waiting for a worker. |
| PROCESSING | Conversion in progress. |
| COMPLETED | Done — the output URL is in the response. |
| FAILED | The job could not be completed; see error. |
SRT to SCC API Pricing
⚡ Performance
Live usage measured on Pixazo's gateway, split by model version. Generation time is how long a generation takes end-to-end (lower is better). Success rate is the percent of generations that complete (higher is better).
〰 Uptime
Percent of generations that succeeded over the selected period, per model version.