Data processing locations
All Dictation audio and transcription data is processed in AWS regions located in the United States and the European Union: US
EU
Which of these locations processes your data depends on the endpoint you call,
as described below.
Endpoints
The request format, headers, and parameters are identical on all three. Only
the host changes.
The global endpoint routes to the nearest available region, so your data may
be processed in any of the US or EU locations listed above. If you need data
to stay in one of those zones, call the US or EU endpoint explicitly rather
than relying on the default.
Which endpoint should I use?
- Optimizing for latency? Use the Global endpoint
(
dictation.assemblyai.com). It routes your request to the region with the fastest response time for you, and needs no configuration change. - Need US data residency? Use the US endpoint
(
dictation.us.assemblyai.com). Your audio and transcription data remains within the US. - Need EU data residency? Use the EU endpoint
(
dictation.eu.assemblyai.com). Your audio and transcription data remains within the EU.
How to use it
Replace the base URL with the endpoint you want. In the Python SDK the base URL comes from thedictation_base_url setting, which defaults to the global
endpoint. The examples below use the US data zone; for the EU data zone,
replace us with eu.
- Python SDK
- Python
- JavaScript
- cURL
Global (default)
US data residency
EU data residency
Pre-warming is per host. A connection warmed against the global endpoint is
no use to a request aimed at a data zone endpoint, so warm the same host you
are about to transcribe against. See
Connection pre-warming.