transcriptDelivered - Successful delivery

View as Markdown
Delivered to your ``callback_url`` once a transcription request submitted with a ``callback_url`` finishes (or after delivery is abandoned on terminal failure). The transcript ``data`` matches the inline (200) response; ``request_id`` is at the top level (not nested under ``data``). Delivery: - ``POST {callback_url}`` with ``Content-Type: application/json``; the body is the JSON shape below. - Up to 3 attempts, with exponential backoff between tries and a 30 s per-request timeout. - Retried on transport errors and on any non-2xx response. After the final attempt the delivery is abandoned (logged server-side; there is no API to query abandoned deliveries). Receiver contract: - Respond with any 2xx to acknowledge and stop retries; any non-2xx triggers a retry until the attempt cap. - Deliveries are not signed and carry no idempotency key — correlate and dedupe on ``request_id``.

Headers

apikeystringOptional
API key required when calling through the API gateway.

Request

This endpoint expects an object.
statusstringRequired
request_idstringRequired
call_uuidstringRequired
dataobjectRequired

Response

Your receiver acknowledges with any 2xx, which stops retries. Any non-2xx triggers a retry until the attempt cap.