SCC to SRT API - Convert SCC to SRT API: Pricing, 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.

SCC to SRT generate request

A Scenarist Closed Caption (.scc) file stores captions as hexadecimal line-21 control codes indexed to SMPTE timecode, which is exactly what broadcast systems need and exactly what HTML5, YouTube, and localization tools cannot parse. Going the other direction, from SCC to SRT, means decoding those control bytes, reconstructing pop-on, roll-up, and paint-on caption rows into discrete text cues, and translating timecode back into the millisecond ranges SubRip expects. The Pixazo caption-convert endpoint handles that decode step and emits a clean .srt file you can drop into any player or translation memory. This unlocks reuse of broadcast caption assets on the open web without re-transcribing, and because the source file is never altered you can re-run the conversion any time. Jobs are processed asynchronously and identified by a request_id.

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.scc","to_format":"srt","source_format":"scc"}'

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

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.scc","to_format":"srt","source_format":"scc"}'

import requests

resp = requests.post(
    "https://gateway.pixazo.ai/media-tools/v1/caption-convert",
    headers={
        "Ocp-Apim-Subscription-Key": "YOUR_API_KEY",
        "Content-Type": "application/json",
    },
    json={
  "subtitle_url": "https://example.com/input.scc",
  "to_format": "srt",
  "source_format": "scc"
},
)
print(resp.json())

const res = await fetch("https://gateway.pixazo.ai/media-tools/v1/caption-convert", {
  method: "POST",
  headers: {
    "Ocp-Apim-Subscription-Key": "YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"subtitle_url":"https://example.com/input.scc","to_format":"srt","source_format":"scc"}),
});
console.log(await res.json());

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

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.

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.srt",
    "media_type": "SRT"
  },
  "error": null,
  "created_at": "2026-01-01T00:00:00Z",
  "completed_at": "2026-01-01T00:00:04Z"
}

Response Fields

Status Values