Happy Scribe · Rate Limits

Happyscribe Rate Limits

Happy Scribe does not publish fixed numeric per-minute request limits for its REST API in the public developer documentation. The practical constraint on usage is economic rather than a request-rate cap: transcription, subtitling, and translation consume AI credits (per minute of media) or human-service credits from your plan balance, so throughput is governed by your subscription allowance and topped-up credits. Long-running work is asynchronous - create an order or export, then poll its state or wait for a webhook - so clients should poll at a reasonable interval and back off rather than tight-loop.

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

It captures 4 rate-limit definitions, measuring requests and minutes.

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

Tagged areas include Audio Transcription, Transcription, Subtitles, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Audio TranscriptionTranscriptionSubtitlesRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the REST API.
AI Credit Allowance account
minutes
per plan
Automatic transcription/subtitling/translation draws down per-minute AI credits from your plan and top-ups.
Human Service Allowance account
minutes
pay-per-use
Professional (human) transcription and subtitling is billed per minute against balance.
Export Polling resource
requests
client-controlled
Exports and orders are asynchronous; poll state at a reasonable interval or use webhooks.

Policies

Webhooks over Polling
Register a webhook to receive an HTTP callback when a transcription completes, instead of polling.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on 429 responses.
Credit-Governed Throughput
Effective throughput is bounded by plan AI/human credit balance rather than a per-minute request cap.

Sources