API Documentation
Access the Aevum Zenth ecosystem programmatically. Our RESTful API provides secure, scalable access to 400+ subsidiary services, unified under a single authentication layer and consistent data models.
https://api.aevumzenth.com/v2
All requests must be made over HTTPS. Calls made over plain HTTP will fail. API responses are returned in JSON format unless otherwise specified.
Authentication
Aevum Zenth uses API keys and OAuth 2.0 for authentication. Include your credentials in the Authorization header.
API Key Authentication
Generate keys in your dashboard. Keys are scoped per division (e.g., energy:, finance:, aerospace:).
OAuth 2.0 (PKCE)
For user-level access to sensitive endpoints, implement the Authorization Code Flow with PKCE. Tokens expire after 1 hour.
Rate Limits
API limits are tiered based on your integration level. Default limits apply if no tier is specified.
| Tier | Requests/Min | Burst | Concurrent |
|---|---|---|---|
| Developer | 120 | 30 | 5 |
| Production | 1,200 | 150 | 50 |
| Enterprise | 10,000+ | 500 | 200 |
Headers X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After are included in every response.
Companies
Retrieve a paginated list of active subsidiary companies.
| Parameter | Type | Description |
|---|---|---|
page | integer | Page number (default: 1) |
limit | integer | Items per page (max: 100) |
division | string | Filter by division slug |
curl "https://api.aevumzenth.com/v2/companies?division=energy" \ -H "Authorization: Bearer $ZENTH_API_KEY"
Force a data synchronization for a specific subsidiary across internal ledgers.
Transactions
Initiate a cross-divisional financial transaction. Supports internal settlement and external routing.
| Parameter | Type | Required | Description |
|---|---|---|---|
source_division | string | Yes | Origin division ID |
target_division | string | Yes | Destination division ID |
amount | number | Yes | Transaction value in USD |
metadata | object | No | Custom key-value pairs |
Error Handling
The API uses standard HTTP status codes and returns machine-readable error objects.
Error response format:
{
"error": {
"code": "invalid_api_key",
"message": "The provided API key has expired or is revoked.",
"details": null,
"request_id": "req_8x9m2k4p1"
}
}