Guides

Regional endpoints and compliance

Regional endpoint strategy

The ScalePad API is served from multiple regional edges. Each ScalePad tenant is provisioned into a single region, and that tenant's data lives only in that region. To reach a tenant, you must call the regional hostname that matches where the tenant was provisioned.

US (default)
Hostnameapi.scalepad.com(aliasus.api.scalepad.com)
Products in this regionCore, Lifecycle Manager, Quoter, ControlMap, BackupRadar (/backup-radar/)
EU
Hostnameeu.api.scalepad.com
Products in this regionControlMap, BackupRadar (/backup-radar/)
CA
Hostnameca.api.scalepad.com
Products in this regionControlMap
AU / AP
Hostnameau.api.scalepad.com
Products in this regionControlMap
api.scalepad.com and us.api.scalepad.com resolve to the same US edge.

BackupRadar uses the unified gateway (/backup-radar/)

Integrators reach BackupRadar through the same regional ScalePad gateway as other products, using the /backup-radar/ path prefix (for example https://api.scalepad.com/backup-radar/..., https://eu.api.scalepad.com/backup-radar/...).

US (default)
Consumer base URLhttps://api.scalepad.com/backup-radar/
EU
Consumer base URLhttps://eu.api.scalepad.com/backup-radar/
BackupRadar is not deployed on the CA or AU regional gateways. Use the EU consumer base above for EU-provisioned tenants; the US base will not serve EU tenant data.

The default endpoint resolves to US

api.scalepad.com is the US endpoint.

Every example in our reference docs uses api.scalepad.com for brevity, but that hostname routes only to US infrastructure. API keys authenticate the same way against any region, but each tenant's data lives only in its provisioned region — so calling api.scalepad.com for an EU, CA, or AU tenant will not return that tenant's data.

Customers with EU, Canadian, or Australian data residency requirements must call their regional hostname.

Product availability by region

ControlMap is deployed to every region. BackupRadar is available in US and EU only, via /backup-radar/ on the regional gateway hostnames below; it is not deployed in CA or AU. Core, Lifecycle Manager, and Quoter remain US-only on the default hostname.

Product
US
EU
CA
AU
Core API
✓api.scalepad.com
—
—
—
Lifecycle Manager
✓api.scalepad.com
—
—
—
Quoter
✓api.scalepad.com
—
—
—
ControlMap
✓api.scalepad.com
✓eu.api.scalepad.com
✓ca.api.scalepad.com
✓au.api.scalepad.com
BackupRadar
✓api.scalepad.com/backup-radar
✓eu.api.scalepad.com/backup-radar
—
—
A request to a regional hostname where the product is not deployed (for example, https://eu.api.scalepad.com/core/v1/clients) or where BackupRadar is not offered (for example, https://ca.api.scalepad.com/backup-radar/...) will not be served.

Example requests per region

The same ControlMap endpoint, called against each regional edge:

US

GET https://api.scalepad.com/controlmap/v1/clients/health HTTP/1.1
accept: application/json
x-api-key: <API_KEY>

EU

GET https://eu.api.scalepad.com/controlmap/v1/clients/health HTTP/1.1
accept: application/json
x-api-key: <API_KEY>

CA

GET https://ca.api.scalepad.com/controlmap/v1/clients/health HTTP/1.1
accept: application/json
x-api-key: <API_KEY>

AU

GET https://au.api.scalepad.com/controlmap/v1/clients/health HTTP/1.1
accept: application/json
x-api-key: <API_KEY>

US-only product (Core API)

Products that are not deployed regionally answer only on the US edge:

GET https://api.scalepad.com/core/v1/clients HTTP/1.1
accept: application/json
x-api-key: <API_KEY>

BackupRadar (US and EU)

Use the regional gateway with the /backup-radar/ prefix. Replace the path after the prefix with the operation from your BackupRadar API contract.

GET https://api.scalepad.com/backup-radar/v1/backups HTTP/1.1
accept: application/json
x-api-key: <API_KEY>
GET https://eu.api.scalepad.com/backup-radar/v1/backups HTTP/1.1
accept: application/json
x-api-key: <API_KEY>

Compliance considerations

The following is operational guidance about which endpoint to call to keep tenant data within the appropriate jurisdiction. It is not legal advice — consult your own compliance team for obligations specific to your business.

GDPR (European Union)
The EU General Data Protection Regulation requires that personal data of EU data subjects be processed under EU safeguards. ScalePad serves EU tenants from the eu.api.scalepad.com regional gateway—ControlMap on its normal paths and BackupRadar under the /backup-radar/ prefix. EU-provisioned tenants must use that EU gateway; calling the US default api.scalepad.com will not return EU tenant data.
PIPEDA (Canada)
The Personal Information Protection and Electronic Documents Act governs how organizations handle Canadian personal information. ScalePad operates a Canadian data plane at ca.api.scalepad.com for tenants with Canadian residency requirements. Canadian-provisioned tenants must call this hostname.
CCPA (California)
The California Consumer Privacy Act applies to personal information of California residents. CCPA does not impose a data-residency requirement, and the default api.scalepad.com endpoint (US infrastructure) is consistent with serving California residents. CCPA consumer-rights requests (access, deletion, opt-out of sale) are handled through ScalePad's privacy program (see the ScalePad privacy policy) and are not exposed via the public API.

Choosing the right region

To find the region a tenant is provisioned in, check with your ScalePad account administrator or contact ScalePad support. A self-service region-discovery endpoint is planned and will be documented here once it ships.

Updated 22 days ago