It is possible to set or restrict your integration based on geographical location. There are three methods to do this depending on your setup: One is the default, the other two are optional.

Regions

1. CDN deployment endpoint (default)

This is suitable for roughly 80% of integration types and use cases. If your server-side or programmatic integrations experience unexpected latency, try option 2 below. For SDK integrations with unexpected latency, try option 3. 

CDN entry point: https://api.inbenta.io/

This entry point uses CloudFront edge locations, and the request is routed via the geographically closest CDN edge location to the caller, up to the centralized API entry point.

Reference: https://aws.amazon.com/es/cloudfront/features/

2. Regional deployment endpoint (optional)

This is recommended for server-side and programmatic integration to API calls if your data center fits a near and low latency regional endpoint.

Entry points:

• https://api-eu.inbenta.io/ (A) - Geographically deployed entry point in Europe (Ireland, IE-IRL)
• https://api-us.inbenta.io/ (B) - Geographically deployed entry point in the United States (Virginia, US-USA)
• https://api-br.inbenta.io/ (C) - Geographically deployed entry point in Brazil (Sao Paulo, BR-BRA)
• https://api-au.inbenta.io/ (D) - Geographically deployed entry point in Australia (Sydney, AU-AUS)
• https://api-jp.inbenta.io/ (E) - Geographically deployed entry point in Japan (Tokio, JP-JPN)

Map: https://mapfling.com/qb68w8i

3. Latency-based by DNS resolver endpoint (optional)

This solution works best for SDK-only integrations, where all requests come from various client/browsers spread over the world. Use this if the main deployment (CDN, option 1 above) does not fit your requirements.

Entry point: https://api-smart-routing.inbenta.io/

The routing is based on the regional entry point that gives the user the fastest response with the lowest network latency.