API Documentation

Welcome to the Aevum Zenth Conglomerate API. Our platform provides unified programmatic access to cross-divisional data streams, telemetry ingestion, analytics reporting, and enterprise orchestration across 400+ subsidiaries.

Authentication

All requests to the Aevum Zenth API must be authenticated. You can obtain credentials through the Developer Portal or your Enterprise Dashboard.

API Key

Include your API key in the Authorization header:

# Replace YOUR_API_KEY with your actual key
curl -X GET "https://api.aevumzenth.com/v3/divisions" \
  -H "Authorization: ApiKey YOUR_API_KEY" \
  -H "Content-Type: application/json"

import requests

headers = {
    "Authorization": "ApiKey YOUR_API_KEY",
    "Content-Type": "application/json"
}

response = requests.get("https://api.aevumzenth.com/v3/divisions", headers=headers)
print(response.json())

const axios = require('axios');

const response = await axios.get(
  'https://api.aevumzenth.com/v3/divisions',
  {
    headers: {
      'Authorization': 'ApiKey YOUR_API_KEY',
      'Content-Type': 'application/json'
    }
  }
);
console.log(response.data);

Bearer Token (OAuth 2.0)

For service-to-service communication, use OAuth 2.0 Client Credentials flow. Tokens expire after 3600 seconds.

# Obtain token
curl -X POST "https://auth.aevumzenth.com/oauth/token" \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -H "Content-Type: application/x-www-form-urlencoded"

Base URL & Versioning

All API requests must be made to:

https://api.aevumzenth.com/v3

Major version bumps may introduce breaking changes. We recommend pinning to v3 and monitoring our changelog for updates. Minor/patch updates are backward-compatible.

Core Endpoints

{
  "data": [
    {
      "id": "div_aev_energy_01",
      "name": "Aevum Energy & Power",
      "sector": "Energy",
      "status": "active",
      "api_version": "3.2.1",
      "endpoints_base": "https://api.aevumzenth.com/v3/divisions/div_aev_energy_01"
    }
  ],
  "pagination": {
    "page": 1,
    "limit": 25,
    "total": 400
  }
}

{
  "status": "queued",
  "batch_id": "zth_batch_8f9a2c",
  "records_accepted": 245,
  "processing_eta": "12s"
}

Error Codes

The API uses standard HTTP status codes and returns detailed error objects in the response body.

Error Response Format

{
  "error": {
    "code": "ZTH-400",
    "message": "Invalid payload: 'division_id' must match pattern ^div_[a-z0-9_]+$",
    "details": [
      {
        "field": "division_id",
        "issue": "format_mismatch"
      }
    ],
    "request_id": "zth_req_9a8b7c"
  }
}

Rate Limits

API access is governed by tier-based rate limiting. Limits are applied per API key and reset according to the specified window.

Rate limit headers are included in every response:

• X-RateLimit-Limit: Maximum requests allowed
• X-RateLimit-Remaining: Requests left in current window
• X-RateLimit-Reset: Unix timestamp when the window resets

SDKs & Libraries

Official client libraries are available for rapid integration. All SDKs are open-source and maintained by the Zenth Developer Experience team.

Webhooks

Register webhook endpoints to receive real-time events for divisional updates, data processing completions, and alert triggers.

Event Types

• division.status_changed - Operational status updates
• data.ingest.complete - Batch processing finished
• analytics.report.ready - Generated report available
• security.alert.triggered - Policy or anomaly detection

Webhook Signature Verification

All webhooks include a X-Aevum-Signature header. Verify using HMAC-SHA256 with your webhook secret:

import hmac
import hashlib

def verify_webhook(payload, signature, secret):
    expected = hmac.new(
        secret.encode(),
        payload,
        hashlib.sha256
    ).hexdigest()
    return hmac.compare_digest(expected, signature)