From Gladia's cloud API

The Gladia Enterprise API is Gladia’s Live V2 API. To move an integration:

1. Create an API key in Gladia Workspace (Authentication).
2. Change the base URL: api_url / apiUrl in the SDKs (or GLADIA_API_URL), or the host of your HTTP calls: https://eu1.api.gladia.io instead of https://api.gladia.io.
3. Run your tests: the init body, the WebSocket messages, callbacks and the history are the same.

What is the same

POST /v2/live and its body, the WebSocket protocol and its messages, messages_config, callbacks and their payloads, GET /v2/live, GET /v2/live/{id}, DELETE /v2/live/{id}, GET /v2/live/{id}/file, error bodies.

What differs

	Gladia Enterprise
Models	solaria-3, solaria-1, trantoria-1, with latency profiles
endpointing when omitted	0.64 s (Endpointing)
maximum_duration_without_endpointing when omitted	no limit
Acknowledgments	sent once the audio is transcribed, not on receipt: this makes reconnections lossless
Recordings	FLAC instead of WAV, for accounts that record
History pagination	follow next (a cursor); offset up to 1,000, limit up to 100
region	the region is the API address you call (Regions)
Pre-recorded API (/v2/pre-recorded, /v2/upload)	not available
Summarization, chapterization	not available: accepted, ignored
pre_processing	accepted, not applied

Extensions

Options that only the Gladia Enterprise API knows. Do not send them to Gladia’s cloud API.

option
profile	latency profile
end_of_turn	end-of-turn detection
turn_router	turns off the number hold
numerals	numbers as digits
punctuation	turns off punctuation
diarization, diarization_config	speaker diarization on live audio
named_entity_recognition	entities, with options
pii	PII redaction
GET /v2/live/defaults	the values of omitted options