Sonix · Rate Limits

Sonix Rate Limits

Sonix does not publish fixed numeric request-rate limits for its REST API. Practical throughput is governed by two things: your plan's transcription / translation and AI-workspace hour allowances (per-hour on pay-as-you-go, or the bundled monthly hours on Core/Advanced/Pro), and per-request constraints such as the 100MB multipart upload size (larger files must be supplied via a file_url). Media listing is paginated at 100 items per page. Transcription is asynchronous, so clients should poll media/transcript status or use a completion webhook rather than issuing tight request loops.

Sonix Rate Limits is the machine-readable rate-limit profile for Sonix on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests, hours, bytes, and items.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Audio Transcription, Transcription, Speech-to-Text, Rate Limiting, and Quotas.

6 Limits Throttle: 429
Audio TranscriptionTranscriptionSpeech-to-TextRate LimitingQuotas

Limits

API Request Rate account
requests
not published
No fixed numeric per-minute request-rate limit is documented for the REST API.
Transcription / Translation Hours account
hours
per plan
Per-hour on pay-as-you-go ($10/hr); bundled monthly hour allowances on Core/Advanced/Pro.
AI Workspace Hours account
hours
per plan
AI analysis (summaries, chapters, sentiment, entities) draws down a separate monthly AI-workspace hour allowance.
Multipart Upload Size request
bytes
104857600
Multipart file uploads are limited to 100MB; larger or remote files must be passed via file_url.
Media List Pagination request
items
100
The media list endpoint returns up to 100 items per page and includes total_pages.
Storage account
bytes
per plan
Storage quota ranges from 5 GB (pay-as-you-go) to 100 GB (Pro) by plan.

Policies

Asynchronous Processing
Transcription, translation, exports, and AI analysis are asynchronous jobs; retrieve results by polling status or via a completion webhook (callback_url).
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses rather than polling aggressively.

Sources