---
updatedAt: 2026-05-14T10:04:07.000Z
---
Fetch the complete documentation index at: https://docs.talkdesk.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.
# App and Talkdesk Regions
Talkdesk deploys in multiple geographic locations for two reasons:
* To provide a robust service for all our customers, regardless of their place of operation.
* To comply with restrictions on data locality driven by privacy-related legislation imposed in several countries.
## Supported Regions and Base URLs
Talkdesk currently supports regions:
* US -
* Europe -
* Canada -
* UK -
* FedRAMP Base URL -
If you are using [Talkdesk APIs](https://docs.talkdesk.com/docs/api-access) only within your Talkdesk account, you can use the hard-coded region-specific URLs.\
However, if you are [registering an app](https://docs.talkdesk.com/docs/app-enablement) intended to be used by all Talkdesk customers, you must ensure to subscribe to the [provisioning events](https://docs.talkdesk.com/reference/app-installed). These events always include a `_links` field that contains [relevant URLs concerning the event in question](https://docs.talkdesk.com/docs/how-to-guarantee-your-app-works-in-all-regions#event-payload-key-values-description-within-_links). Use these URLs over the hard-coded ones as you operate because they already consider region specificity.
For example, to [access Talkdesk APIs](https://docs.talkdesk.com/docs/api-access#accessing-the-talkdesk-apis), the `root` field within `_links` contains a region-dependent URL (Talkdesk API Gateway). The values `root` may have are outlined above.
> 👍
>
> Using the URLs provided within each event allows your app to work seamlessly in the defined region.
## Event Payload Key Values Description (within \_`links`)
[block:parameters]
{
"data": {
"h-0": "URL Key",
"h-1": "Value Description",
"h-2": "Events Containing the URL",
"0-0": "`root`",
"0-1": "Talkdesk API Gateway URL. The value of this URL varies according to the operating region. It is the prefix (base URL) to be used to access Talkdesk APIs.",
"0-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed) \n \n[app.updated](https://docs.talkdesk.com/reference/app-updated) \n \n[app.unistalled](https://docs.talkdesk.com/reference/appuninstalled) \n \n[app.trial_started](https://docs.talkdesk.com/reference/apptrial_started) \n \n[app.trial_extended](https://docs.talkdesk.com/reference/apptrial_extended) \n \n[app.trial_ended](https://docs.talkdesk.com/reference/apptrial_ended) \n \n[user.logout](https://docs.talkdesk.com/reference/userlogout) \n \n[app.credentials_rotated](https://docs.talkdesk.com/reference/appcredentials_rotated)",
"1-0": "[`userinfo`](https://docs.talkdesk.com/reference/reference/usersme)",
"1-1": "Provides a URL that can be used to get information about yourself as a user, regarding an action you executed leading to the event/response",
"1-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed)",
"2-0": "`user`",
"2-1": "Provides a URL that can be used to get information about the user that executed the action leading to the event/response",
"2-2": "[user.logout](https://docs.talkdesk.com/reference/userlogout)",
"3-0": "`self`",
"3-1": "Provides more information about the requested resource (it may vary from event to event). E.g.: event name, timestamp, payload, etc.",
"3-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed) \n \n[app.updated](https://docs.talkdesk.com/reference/app-updated) \n \n[app.unistalled](https://docs.talkdesk.com/reference/appuninstalled) \n \n[app.trial_extended](https://docs.talkdesk.com/reference/apptrial_extended) \n \n[app.trial_ended](https://docs.talkdesk.com/reference/apptrial_ended) \n \n[user.logout](https://docs.talkdesk.com/reference/userlogout) \n \n[app.credentials_rotated](https://docs.talkdesk.com/reference/appcredentials_rotated)",
"4-0": "`installation`",
"4-1": "Can be used as an endpoint if you need more information about installation data",
"4-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed) \n \n[app.unistalled](https://docs.talkdesk.com/reference/appuninstalled) \n \n[app.trial_started](https://docs.talkdesk.com/reference/apptrial_started) \n \n[app.trial_extended](https://docs.talkdesk.com/reference/apptrial_extended) \n \n[app.trial_ended](https://docs.talkdesk.com/reference/apptrial_ended) \n \n[user.logout](https://docs.talkdesk.com/reference/userlogout) \n \n[app.credentials_rotated](https://docs.talkdesk.com/reference/appcredentials_rotated)",
"5-0": "`authorization`",
"5-1": "Allows requesting and receiving an [authorization code](https://docs.talkdesk.com/docs/authorization-code) from Talkdesk that can be used to generate refresh and access tokens using the URL provided in `tokens`",
"5-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed)",
"6-0": "`tokens`",
"6-1": "Generates refresh and access tokens given an authorization code or a set of [client credentials](https://docs.talkdesk.com/docs/client-credentials)",
"6-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed)",
"7-0": "`widget_url`",
"7-1": "A reference to a JavaScript snippet that must be included on the partner app's [header](https://docs.talkdesk.com/docs/talkdesk-header). The snippet may vary if the customer is using a Talkdesk reseller, so you can't just use the hard coded snippet. You can count on the provided header to have 32px.",
"7-2": "[app.installed](https://docs.talkdesk.com/reference/app-installed)"
},
"cols": 3,
"rows": 8,
"align": [
"left",
"left",
"left"
]
}
[/block]
> 📘
>
> See the [Events API documentation](https://docs.talkdesk.com/docs/events-api) for more information.
> 🚧 Troubleshooting
>
> If you have questions or technical issues, please open a ticket using [this form](https://support.talkdesk.com/hc/en-us/requests/new).