The Ingest API lets you submit media files for transcription by providing a source URL. Trint downloads the file, transcribes it, and notifies you at each stage via webhook callbacks.

How it works

Submit — POST /ingest with a sourceUrl. You receive an operationToken to track the operation.
Track — If you provided a callbackUrl, Trint sends webhook events as the upload progresses: download, transcription, completion or failure.
Poll — GET /ingest to list uploads with filters and pagination, or GET /ingest?view=summary for aggregate status counts.

Authentication

All requests require Basic authentication using your API Key v2 credentials:

Authorization: Basic <base64(KEY_ID:KEY_SECRET)>

Only API Key v2 and Bearer tokens are accepted. API Key v1 is not supported.

Operation token

Every ingest request returns a unique operationToken. This token is:

Included in the 202 Accepted response
Sent with every webhook callback
Used as the identifier when querying upload status

Use it to correlate requests, callbacks, and status queries end-to-end.

Webhook lifecycle

If you provide a callbackUrl, your endpoint receives these events in order:

Event	Description
`ACTIVITY_STARTED`	Ingest operation has begun
`MEDIA_TRANSFER_COMPLETE`	Media downloaded successfully
`TRANSCRIPT_COMPLETE`	Transcription finished

On failure, you receive MEDIA_TRANSFER_FAILED or TRANSCRIPT_FAILED instead.

Your callback endpoint must return 200 OK to the initial ACTIVITY_STARTED event. A non-200 response or timeout will abort the upload.

Status values

Uploads progress through these statuses:

Status	Description
`pending`	Queued, waiting to be processed
`importing`	Downloading media from the source URL
`processing`	Transcribing the media
`ready`	Transcription complete
`failed`	An error occurred