> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenshotmax.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Domains

> Understand the regional API domains available for ScreenshotMAX.

ScreenshotMAX exposes multiple API domains to keep your integrations fast regardless of where your infrastructure lives. Each domain serves the exact same product features and enforces the same usage quotas—the only difference is the physical location of the servers that handle your requests.

## Available domains

| Domain                     | Region                  | Location |
| -------------------------- | ----------------------- | -------- |
| `api.screenshotmax.com`    | North America (default) | USA      |
| `api-us.screenshotmax.com` | North America           | USA      |
| `api-eu.screenshotmax.com` | Europe                  | Belgium  |
| `api-as.screenshotmax.com` | Asia                    | Taiwan   |

* **`api.screenshotmax.com`** automatically routes to the North America (USA) region. It is ideal if your workloads are already based in North America or you do not need a specific regional endpoint.
* **`api-us.screenshotmax.com`** explicitly targets the **North America** region and is equivalent to the default `api` domain.
* **`api-eu.screenshotmax.com`** keeps traffic inside the **European Union** with infrastructure located in Belgium.
* **`api-as.screenshotmax.com`** serves the **Asia-Pacific region** from data centers in Taiwan.

## Choose the closest domain

For the lowest possible latency, pick the subdomain that is geographically closest to the systems making requests to the ScreenshotMAX API. This minimises the physical distance your network packets must travel and helps deliver faster response times.

No matter which domain you select, you will benefit from:

* Identical API surface and capabilities.
* The same authentication, rate limits, and quota accounting.
* Consistent behaviour, responses, and SLAs.

If you need to switch regions in the future, simply update the base URL used by your integration—no other code changes are required.