When to use this runbook
Use after preflight selectstranscription-lite and every requested feature exists in the current Lite input schema.
When not to use it
Do not use Lite for primary-only LLM, insight, custom-vocabulary, classification, or translated-SRT fields. Do not resubmit an uncertain/failed job automatically or cancel without explicit user intent.Required inputs
SALAD_API_KEYandSALAD_ORGANIZATION.- For a new submission, a trusted downloadable
SALAD_MEDIA_URLand exact approved Lite fields: requiredurland optionallanguage_code,return_as_file, timestamp, diarization,srt, ortranslatesettings. - Optional non-secret caller metadata and webhook URI.
- A caller-defined polling attempt and elapsed-time budget.
- For an existing job,
SALAD_TRANSCRIPTION_LITE_JOB_ID, obtained only from a successful create response,Location, or trusted record.
Authoritative sources
Use
api-specs/transcription-lite.json; the same operation IDs also occur in other specifications.
Dynamic values to retrieve
- Current Lite endpoint metadata and price description.
- The create response ID,
Location, status, events, and timestamps. - Current job status/events/output during verification.
- Current source-URI accessibility and rate-limit response.
Preflight checks
- Complete Choose a Transcription API and Preflight.
- Confirm the path contains
/transcription-lite/and the endpoint read succeeds. - Validate against
CreateSaladCloudTranscriptionLiteAPIJob;input.urlis required. - Reject primary-only and undocumented fields, including
audio_stream_index,multichannel,enhanced_accuracy,summarize, LLM/classification fields, custom vocabulary, andsrt_translation. - The Lite
language_codeschema has no enum. Require a caller-approved value and do not claim arbitrary strings are supported. - If a trusted application record already has a job ID, read it instead of creating another.
- Define terminal and polling predicates before submission.
Procedure
Read the Lite endpoint immediately before submitting this schema-derived request:Location from the 201 response.
Poll the exact Lite job:
succeeded, verify required text, duration, and processing_time, plus any requested timestamps or SRT fields.
The schema does not define the alternative file-URL shape described by canonical return_as_file guidance; use and
redact the live response without inventing property names.
For cancellation, read immediately before delete_inference_endpoint_job, require explicit intent, then verify with the
exact get operation within the polling budget.
Decision rules
Expected states and responses
Create returns201, reads return 200, and cancellation returns 202. States are pending, running, succeeded,
cancelled, and failed; events use created, started, succeeded, cancelled, and failed.
Retry behavior
Retry only reads for plausible transient transport,429, or server failures within a fixed budget, honoring
Retry-After when present. Never retry an uncertain create without an ID, automatically resubmit a failed job, or retry
cancellation without a fresh read and the original intent.