Base URL Configuration & Regional Routing
Configure your integration base URLs, understand regional endpoint routing, and ensure compliance with data residency requirements across Aevum Zenth's global infrastructure.
Architecture Overview
All Aevum Zenth services route through our global Anycast CDN. Base URLs automatically resolve to the nearest regional edge node based on latency, compliance requirements, and failover status.
https://{region}.api.aevumzenth.com/v{version}/{service}
Replace {region} with a supported geographic identifier, {version} with 2 or 3 (current), and {service} with the target division API.
Regional Configuration
| Region Code | Base URL | Data Center | Compliance |
|---|---|---|---|
| us-east | https://us-east.api.aevumzenth.com/v3 | Virginia, US | SOC2, HIPAA, CCPA |
| us-west | https://us-west.api.aevumzenth.com/v3 | Oregon, US | SOC2, FedRAMP Moderate |
| ca-central | https://ca-central.api.aevumzenth.com/v3 | Toronto, CA | PIPEDA, SOC2 |
| sa-east | https://sa-east.api.aevumzenth.com/v3 | São Paulo, BR | LGPD, ISO 27001 |
| Region Code | Base URL | Data Center | Compliance |
|---|---|---|---|
| eu-west | https://eu-west.api.aevumzenth.com/v3 | Ireland | GDPR, UK GDPR, ISO 27001 |
| eu-central | https://eu-central.api.aevumzenth.com/v3 | Frankfurt, DE | GDPR, BSI C5 |
| me-central | https://me-central.api.aevumzenth.com/v3 | Dubai, AE | ISO 27001, local data laws |
| Region Code | Base URL | Data Center | Compliance |
|---|---|---|---|
| ap-northeast | https://ap-northeast.api.aevumzenth.com/v3 | Tokyo, JP | APPI, ISO 27001 |
| ap-southeast | https://ap-southeast.api.aevumzenth.com/v3 | Singapore | PDPA, MAS TRM |
| ap-southeast-2 | https://ap-southeast-2.api.aevumzenth.com/v3 | Sydney, AU | APP, ISO 27001 |
| Region Code | Base URL | Data Center | Compliance |
|---|---|---|---|
| gov-us | https://gov-us.api.aevumzenth.com/v3 | GovCloud (US) | FedRAMP High, IL5/6 |
| gov-eu | https://gov-eu.api.aevumzenth.com/v3 | EuCC Certified | EUCC, GDPR-Enhanced |
Service Routing Matrix
Append service paths to the regional base URL. All endpoints support mutual TLS (mTLS) and OAuth 2.0 client credentials.
| Division | Service Path | Example Request |
|---|---|---|
| Energy & Power | /energy/grid | GET /v3/energy/grid/status?region=eu-west |
| Digital Systems | /compute/instances | POST /v3/compute/instances |
| Aerospace | /telemetry/satellite | GET /v3/telemetry/satellite/{id} |
| Health Sciences | /genomics/analysis | POST /v3/genomics/analysis/jobs |
| Capital Group | /finance/trading | POST /v3/finance/trading/orders |
| Logistics | /freight/track | GET /v3/freight/track?carrier=zenth-global |
Data Residency & Failover
Data routed to a specific regional base URL never leaves that geographic boundary unless explicitly configured for cross-region replication. All persistence layers use region-scoped storage classes.
POST /v3/resource/create HTTP/1.1\r\nHost: eu-west.api.aevumzenth.com\r\nX-AZ-Data-Residency: strict\r\nContent-Type: application/json
Setting X-AZ-Data-Residency: strict enforces hard boundary routing. Requests violating this header return 403 FORBIDDEN with code AZ.RESIDENCY.VIOLATION.
Rate Limits & Throttling
| Tier | Requests / Minute | Burst Allowance | Response Header |
|---|---|---|---|
| Standard | 1,000 | +20% | X-RateLimit-Remaining |
| Enterprise | 10,000 | +50% | X-RateLimit-Remaining |
| Strategic Partner | Unlimited | Dedicated Pool | X-RateLimit-Pool |
Rate limits are evaluated at the edge node. Throttled requests receive 429 Too Many Requests with a Retry-After header in seconds.