API Access & Integration
Connect your applications to Aevum Zenth's global infrastructure. Generate keys, monitor usage, and integrate across all 400+ divisions.
All API requests require a valid API key passed in the `Authorization` header. Use the sandbox environment for testing before switching to production.
Aevum Zenth uses a hybrid auth model combining API keys for server-to-server communication and OAuth 2.0 for user-delegated access.
- API Keys: Long-lived tokens for backend services. Never expose in client-side code.
- OAuth 2.0: Required for accessing user-specific data across Healthcare, Finance, and Real Estate divisions.
- Webhooks: Real-time event streaming with HMAC-S256 signature verification.
Create a new key for your application. You'll be able to set scopes and environment restrictions.
⚠️ Keys are only shown once during creation. Generate a new key if lost.
| Method | Endpoint | Description | Status |
|---|---|---|---|
| GET | /v2/divisions | List all active division categories and metadata | Live |
| GET | /v2/energy/grid/{id} | Retrieve real-time smart grid metrics and efficiency data | Live |
| POST | /v2/logistics/freight | Submit autonomous freight routing requests | Live |
| PUT | /v2/healthcare/patients/{id}/vitals | Update precision medicine telemetry (OAuth required) | Beta |
| GET | /v2/aerospace/orbits | Query satellite constellation positions and downlink status | Live |
| DELETE | /v2/webhooks/{id} | Remove registered event subscription | Dep. |
API access is governed by tiered rate limiting to ensure global infrastructure stability. Enterprise plans unlock dedicated throughput.
⚠️ Limit Exceeded (429)
When limits are reached, the API returns a `429 Too Many Requests` response with a `Retry-After` header. Implement exponential backoff with jitter in your retry logic.