Skip to main content
In order to provide a smooth experience and optimal performance for all users, Gladia provides 3 plans:

​
Hitting your concurrency limit

When you hit your concurrent session limit, both the Live and Pre-recorded APIs return a 429 status code.
Prefer the official SDK for Live integrations: it already handles the WebSocket lifecycle (reconnection, session continuity, retries, buffering, and related timing). See the Live quickstart.
For pre-recorded jobs, a 200 on POST or a transcription.created webhook means the job was accepted — do not resubmit while it is still queued or processing. See Transcription process & retry policy.

​
Default values

Any limit above the default requires a capacity check. Contact the sales team to request an increase.
  • Usage : New accounts receive a one-time grant of €50 in credits. These credits do not renew once consumed. When they run out, top up your wallet or upgrade to a paid plan to continue.
  • Concurrency : (depending on free/paid tier) This refers to the maximum number of transcription (pre-recorder or real-time) that a user can process at the same time. For asynchronous transcriptions, Paid plan users can queue up to 300 requests, but only will still have 25 max processed concurrently.
  • Realtime session duration : (all plans) A single realtime (live) transcription session cannot exceed 3 hours. After 3 hours, the session will be terminated. For longer events, start a new session when approaching the limit.
  • API level rate limit : (same for every user) Which is the number of API calls that a user can make within a particular time frame. This is to ensure that a single user or malicious actor doesn’t affect the performance of the API for all the other users.