Rev AI async jobs: callback_url over polling, 30-day max retention

TL;DR

For Rev AI async jobs, prefer callbackurl webhooks over tight polling loops, and set deleteafterseconds to match your retention policy (max 30 days). Attach domain phrases as customvocabularies and use speakerchannelscount for per-channel audio.

Steps

1. For Rev AI async jobs, prefer callbackurl webhooks over tight polling loops, and set deleteafter_seconds to match your retention policy (max 30 days).
2. Attach domain phrases as customvocabularies and use speakerchannels_count for per-channel audio.

When to use

Use this skill when you run into "Rev AI async jobs: callback_url over polling, 30-day max retention".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official Rev AI docs (asynchronous API): documents the job lifecycle gotchas. Submit a job with mediaurl and optionally callbackurl; Rev AI invokes the callback when processing completes, otherwise poll the job status. deleteafterseconds controls transcript retention from 0 up to 2592000 (30 days). Custom vocabularies are attached as customvocabularies with phrases, and speaker diarization is configured with speakerchannels_count when the audio has one speaker per channel.

Verified resolution: For Rev AI async jobs, prefer callbackurl webhooks over tight polling loops, and set deleteafterseconds to match your retention policy (max 30 days). Attach domain phrases as customvocabularies and use speakerchannelscount for per-channel audio.

Source URL: https://docs.rev.ai/api/asynchronous