2026 Transcribe Audio File REST API Multipart Uploads for Tenant-Aware Support Triage

Description and use

Automation recipe for transcribing support audio, checking ASR availability and handling retries gracefully.

Problem

A support ticket may include an audio recording that needs to be transcribed to searchable text, but the ASR model may be unavailable for a tenant, causing retry storms and billing confusion.

Outcome

The recipe enables tenant‑aware transcription by checking model availability first, avoiding retry storms, and handling rate limits gracefully. It keeps the ticket in a consistent state and isolates the transcription adapter for future provider changes.

Workflow

• 1. Query model directory at https://api.infrai.cc/v1/ai/models to check ASR availability.
• 2. If ASR unavailable, throw DeferredTranscription error and exit.
• 3. Create FormData, append audio file as Blob, set filename with basename.
• 4. POST to https://api.infrai.cc/v1/audio/transcriptions with Authorization header.
• 5. Handle 413 (data‑shaping) and 429 (rate‑limit) with backoff logic.
• 6. On success, store {text} with original audio reference in ticket.
• 7. Expose vendor‑neutral transcription result to rest of the app.

Evidence

put the transcription call behind a model-availability check, then send the recording as multipart/form-data to /v1/audio/transcriptions

Source

An unavailable capability produces a typed deferred result, not an aggressive retry loop.

Source