● System Operational

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

HEADER Authorization: Bearer <api_key>

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.

TierRequests/MinBurstConcurrent
Developer120305
Production1,20015050
Enterprise10,000+500200

Headers X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After are included in every response.

Companies

GET /companies

Retrieve a paginated list of active subsidiary companies.

ParameterTypeDescription
pageintegerPage number (default: 1)
limitintegerItems per page (max: 100)
divisionstringFilter by division slug
curl "https://api.aevumzenth.com/v2/companies?division=energy" \
  -H "Authorization: Bearer $ZENTH_API_KEY"
POST /companies/{id}/sync

Force a data synchronization for a specific subsidiary across internal ledgers.

Transactions

POST /transactions

Initiate a cross-divisional financial transaction. Supports internal settlement and external routing.

ParameterTypeRequiredDescription
source_divisionstringYesOrigin division ID
target_divisionstringYesDestination division ID
amountnumberYesTransaction value in USD
metadataobjectNoCustom key-value pairs

Error Handling

The API uses standard HTTP status codes and returns machine-readable error objects.

400
Bad Request — Invalid parameters or malformed JSON
401
Unauthorized — Missing or invalid API key
403
Forbidden — Insufficient division permissions
404
Not Found — Resource does not exist
429
Rate Limited — Too many requests
500
Internal Error — Server-side failure

Error response format:

{
  "error": {
    "code": "invalid_api_key",
    "message": "The provided API key has expired or is revoked.",
    "details": null,
    "request_id": "req_8x9m2k4p1"
  }
}

SDKs & Libraries

Official client libraries are available for rapid integration:

LanguagePackageRepository
Node.js@aevumzenth/sdkGitHub
Pythonzenth-clientPyPI
Gogithub.com/aevumzenth/go-sdkGitHub
Rubyaevum-zenth-rbRubyGems