Givergy operates regional production deployments. Every customer account is hosted in exactly one region, and every endpoint documented here is served by that region’s hostname. Throughout these docs the placeholder {EMS_BASE_URL} stands for the production hostname for your account’s region.
Available regions today
| Region | Production hostname | Demo / sandbox hostname |
|---|
| United Kingdom | https://uk.givergy.com | https://uk.demo.givergy.com |
| United States | https://us.givergy.com | https://us.demo.givergy.com |
| Canada | https://can.givergy.com | https://can.demo.givergy.com |
| Australia | https://aus.givergy.com | https://aus.demo.givergy.com |
| Hong Kong | https://hk.givergy.com | https://hk.demo.givergy.com |
Note the aus prefix for Australia and the can prefix for Canada — both are intentionally three letters, not the two-letter ISO codes.
Coming Soon — additional regions. If your data-residency requirements need a region not listed above, contact support@givergy.com to discuss timelines. Which region am I in?
If you don’t know which region hosts your account, the simplest way to find out is to ask Givergy: support@givergy.com.
Alternatively, the Givergy product UI for your account loads from one of these subdomains. The part before .givergy.com (e.g. us in us.givergy.com) is your region prefix and resolves to the same hostname as the API base URL.
Internally Givergy resolves region from your account locale:
| Account locale | Region |
|---|
en_US | us.givergy.com |
en_CA | can.givergy.com |
en_AU | aus.givergy.com |
en_HK | hk.givergy.com |
| anything else | uk.givergy.com |
White-label hostnames
Some customers operate white-label hostnames (for specific charities or events) that share infrastructure with these regions. Those are not part of the public API surface and should not be hit directly — always call the regional hostname for your account.
Cross-region behavior
The five production hostnames are independent deployments with independent databases. Cross-region queries are not possible — an integration is always scoped to a single region. If you need data from multiple regions, you’ll need separate integrations per region. 
