API Documentation
Interact programmatically with the Aevum Zenth ecosystem. Our RESTful API provides unified access to divisional metrics, global infrastructure, authentication, and real-time telemetry.
division_id parameter to isolate queries. All responses include X-Request-Id for tracing.Overview
The Aevum Zenth API exposes core operational data across 400+ subsidiaries. It supports standard HTTP methods, JSON payloads, and comprehensive webhook event streaming. The API is versioned at the base path level.
Authentication
Authenticate using Bearer tokens issued via the Zenth Identity Platform. Tokens are valid for 24 hours by default and can be refreshed using the /auth/token/refresh endpoint.
Core Endpoints
Primary resource management and telemetry retrieval routes.
| Method | Endpoint | Description |
|---|---|---|
| GET | /divisions | List all active operational divisions |
| GET | /divisions/{id} | Fetch detailed division metadata |
| POST | /divisions/{id}/metrics | Push custom telemetry payloads |
| GET | /global-locations | Retrieve regional HQ & hub coordinates |
| PUT | /webhooks | Register or update webhook endpoints |
| DEL | /sessions/{id} | Revoke API session & tokens |
Official SDKs
Language-native clients with auto-retry, circuit breakers, and typed responses.
Full async/await support, tree-shakeable, and compatible with Node & browsers.
Asyncio-ready, pandas-compatible dataframes, and automatic pagination.
Native goroutine concurrency, context cancellation, and zero-copy parsing.
Error Codes & Handling
Standard HTTP status codes with extended metadata in the X-Zenth-Error header.
| Code | Meaning | Resolution |
|---|---|---|
| 400 | Invalid Request | Check payload schema & required fields |
| 401 | Unauthorized | Refresh token or verify API key scope |
| 403 | Forbidden | Token lacks division-level permissions |
| 429 | Rate Limited | Implement exponential backoff (see limits) |
| 500 | Internal Error | Log X-Request-Id and contact support |