Public API v2.4

Aevum Zenth API Documentation

Access our global operational data, subsidiary networks, and enterprise endpoints. Built for scalability, security, and cross-divisional integration.

Authentication

All API requests require authentication via Bearer tokens. Generate your API key from the Developer Console. Include it in the Authorization header.

HTTP Header

Authorization: Bearer az_live_9f8e7d6c5b4a3210

Token Scopes

Scope	Access Level
`read:divisions`	View operational divisions & public metrics
`read:subsidiaries`	Access subsidiary registry & financial summaries
`write:projects`	Create/update R&D and integration projects
`admin:webhooks`	Configure event listeners & routing

Endpoints

The API follows RESTful conventions. All requests and responses are JSON-encoded. Base URL: https://api.aevumzenth.com/v2

GET /divisions

Retrieve a paginated list of all active conglomerate divisions. Supports filtering by industry, region, and operational status.

Query Parameters

Parameter	Type	Description
`limit`	integer	Results per page (default: 20, max: 100)
`offset`	integer	Pagination offset
`region`	string	ISO 3166-1 alpha-2 or 'global'

Response Example

JSON

{
  "success: true,
  "data: [
    {
      "id: "div_energy_01",
      "name: "Aevum Energy & Power",
      "industry: "Renewables & Fusion",
      "headquarters: "Neo Geneva",
      "status: "active"
    }
  ],
  "meta: {
    "total: 400,
    "page: 1,
    "limit: 20
  }
}

POST /projects

Request Body

JSON

{
  "name: "Orbital Manufacturing Alpha",
  "division_ids: ["div_aerospace_04", "div_research_09"],
  "budget_usd: 125000000,
  "timeline_months: 24,
  "classification: "enterprise"
}

Response Example

JSON

{
  "success: true,
  "data: {
    "id: "proj_8x729f01",
    "status: "created",
    "created_at: "2026-01-15T09:42:00Z",
    "tracking_url: "https://portal.aevumzenth.com/projects/proj_8x729f01"
  }
}

GET /global-nodes/{node_id}

Fetch detailed telemetry, capacity metrics, and operational logs for a specific regional hub or headquarters.

Rate Limits & Throttling

To ensure platform stability, API access is tiered based on authentication scope and subscription level.

Standard: 1,000 requests / minute (burst: 50)
Enterprise: 5,000 requests / minute (burst: 200)
Real-time Webhooks: Unmetered, but subject to 2xx delivery confirmation

Rate limit headers are included in every response:

HTTP Headers

X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4892
X-RateLimit-Reset: 1673928400

Error Handling & Status Codes

The API uses standard HTTP status codes and returns detailed error objects for debugging.

Code	Meaning	Common Cause
`200`	OK	Successful request
`400`	Bad Request	Invalid JSON or missing required fields
`401`	Unauthorized	Missing or expired Bearer token
`403`	Forbidden	Insufficient token scopes
`404`	Not Found	Resource ID does not exist
`429`	Too Many Requests	Rate limit exceeded
`500`	Internal Error	Upstream grid or database failure

Error Response Format

JSON

{
  "success: false,
  "error: {
    "code: "INVALID_SCOPE",
    "message: "Token lacks required 'write:projects' permission.",
    "trace_id: "az_trace_9f82b1c4"
  }
}