API Documentation
Programmatic access to Aevum Zenth's multidivisional infrastructure, analytics, and partner networks.
All API endpoints are served over HTTPS and return JSON responses. Base URL: https://api.aevumzenth.com/v1
Quick Start
curl -X GET "https://api.aevumzenth.com/v1/divisions" \
-H "Authorization: Bearer <YOUR_API_KEY>"
Authentication
Aevum Zenth uses Bearer Token authentication for API access. Include your API key in the Authorization header of every request.
Keep your API keys secure. Keys are scoped to specific divisions and IP whitelisting is enforced by default.
Authorization: Bearer az_live_8x92k4m1p7q0r3s5t6v8w9y2
OAuth2 client credentials flow is also supported for partner integrations. Request tokens via POST /oauth/token.
Rate Limits
| Plan | Requests/min | Burst | Scope |
|---|---|---|---|
| Developer | 60 | 10 | Per IP |
| Enterprise | 1,000 | 100 | Per API Key |
| Partner | 5,000 | 500 | Dedicated Queue |
Rate limit headers are included in every response: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
Endpoints
Returns a paginated list of Aevum Zenth operational divisions with metadata.
Query Parameters
| Param | Type | Required | Description |
|---|---|---|---|
page | integer | No | Page number (default: 1) |
limit | integer | No | Items per page (max: 100) |
region | string | No | Filter by geo region (e.g., `APAC`, `EMEA`) |
GET /v1/divisions?region=APAC&limit=5
Host: api.aevumzenth.com
Authorization: Bearer az_live_...
{
"data": [
{
"id": "div_aerospace_01",
"name": "Aevum Aerospace & Defense",
"region": "APAC",
"status": "active",
"revenue_ytd": 2450000000
}
],
"meta": { "total": 400, "page": 1 }
}
Execute complex analytical queries across operational divisions. Supports real-time and historical data aggregation.
{
"division_ids": ["div_energy_03", "div_tech_12"],
"metrics": ["carbon_footprint", "r_d_spend"],
"date_range": {
"start": "2024-01-01",
"end": "2024-12-31"
},
"aggregation": "monthly"
}
Manually initiate a data synchronization cycle for a specific partner integration. Returns a job ID for polling.
Error Codes
Aevum Zenth uses standard HTTP status codes and extends them with custom error payloads for business logic failures.
| Code | Status | Description |
|---|---|---|
400 | Bad Request | Malformed JSON or missing required parameters |
401 | Unauthorized | Invalid or expired API key |
403 | Forbidden | Insufficient permissions for requested scope |
429 | Too Many Requests | Rate limit exceeded |
500 | Internal Error | Unrecoverable system failure |
AZ-1004 | Division Offline | Requested division is undergoing maintenance |
{
"error": {
"code": "401",
"message": "Invalid API key. Ensure your token has not expired.",
"request_id": "req_9f8e7d6c5b4a"
}
}
SDKs & Tools
Official client libraries are available for rapid integration.
Python
pip install aevum-zenth-sdk
from aevum_zenth import Client
client = Client(api_key="az_live_...")
divisions = client.divisions.list(region="EMEA")
print(divisions)
Node.js
npm install @aevumzenth/sdk