Reference

Regions

Enterprise customers can pin sends to specific geographic regions for data residency and compliance.

Available Regions

Region ID	Location	Notes
`global`	Automatic (default)	Routes to nearest available cluster
`us-east-1`	Virginia, USA	US-based sending, SOC 2 Type II
`us-west-1`	Oregon, USA	US West Coast
`eu-west-1`	Ireland	EU data residency, GDPR-compliant
`eu-central-1`	Frankfurt	Germany, strict EU data rules
`ap-south-1`	Singapore	Asia-Pacific routing
`ap-northeast-1`	Tokyo	Japan / APAC enterprise

Setting a Region

Per-Domain

curl -X PUT https://api.postmta.com/v1/domains/mail.example.com -H "Authorization: Bearer pmta_live_xxxx" -d '{"region":"eu-west-1"}'

Per-Message

{"region":"eu-west-1","from":{"address":"hello@example.com"},"to":[{"address":"alice@example.com"}],"subject":"...","html":"..."}

Data Residency

When you set a region, all data associated with that send stays within that region: message content, metadata, webhook payloads, analytics data, and DKIM keys.