Aevum Zenth Core Platform Documentation

Comprehensive technical reference for integrating with the Aevum Zenth multidivisional operating system. Covers API endpoints, authentication flows, data synchronization protocols, and enterprise SDK usage.

ℹ️ Platform Status
All core systems are operating normally. v2.4 introduces breaking changes to the webhook signature verification process. Please review migration notes.

Quickstart Guide

Initialize a connection to the Core Mesh within 30 seconds using your tenant ID and API key. All requests must be routed through regional edge nodes to ensure sub-50ms latency.

cURL Request
curl -X GET https://api.aevumzenth.com/v2/entities/me \
  -H "Authorization: Bearer az_live_sk_x9k2..." \
  -H "X-Tenant-ID: tenant_8a4f2c" \
  -H "Accept: application/json"

Authentication

The Aevum Zenth platform uses OAuth 2.0 with Bearer token authentication for server-to-server communication. Client-side applications must implement PKCE flow for enhanced security.

Token Type Prefix Scope Expiration
Live Secret Keyaz_live_sk_Full API Access90 days
Test Keyaz_test_sk_Sandbox EnvironmentNever
Service Accountaz_svc_Scoped PermissionsConfigurable
⚠️ Security Notice
Never expose secret keys in client-side code, public repositories, or frontend bundles. Use environment variables and secure vaults (e.g., Aevum Vault, HashiCorp, AWS Secrets Manager).

Entity Management

The entity API provides CRUD operations for all core business objects across divisions. Supports JSON:API specification v1.1 with sparse fieldsets and compound documents.

Response Structure
{
  "data": {
    "id": "ent_9f8a7b6c",
    "type": "corporate_entity",
    "attributes": {
      "name": "Aevum Zenth Conglomerate",
      "division_codes": ["ENG", "FIN", "AER"],
      "compliance_tier": "Tier-1",
      "last_sync": "2026-01-15T08:30:00Z"
    },
    "relationships": {
      "subsidiaries": {
        "links": { "related": "/v2/ent_9f8a7b6c/subsidiaries" }
      }
    }
  }
}

ZenthSync Protocol

ZenthSync enables real-time data propagation across the 400+ subsidiary mesh network. Utilizes a custom binary framing layer over HTTP/2 with delta compression and conflict resolution strategies.

Conflict Resolution Modes

Webhooks & Events

Subscribe to platform events via HTTPS endpoints. All payloads are signed using HMAC-SHA256 with your webhook secret. Timestamp tolerance: ±5 seconds.

Event Schema Example
{
  "event_id": "evt_w9x2k1m4",
  "type": "entity.compliance_updated",
  "timestamp": "2026-01-15T14:22:11Z",
  "data": {
    "entity_id": "ent_9f8a7b6c",
    "changes": {
      "field": "compliance_tier",
      "from": "Tier-2",
      "to": "Tier-1",
      "audit_ref": "aud_x7y8z9"
    }
  }
}

Official SDKs

First-party libraries with native TypeScript, Python, and Go support. Auto-generated from OpenAPI 3.1 spec with full IDE autocomplete.

LanguagePackageRepositoryLatest
TypeScript/JS@aevumzenth/corenpm / GitHub2.4.1
Pythonpy-zenthPyPI / GitHub2.3.8
Gogithub.com/aevumzenth/go-zenthGo Modulesv2.4.0

Error Reference

Standardized HTTP status codes with machine-readable error objects. Always check the error.code field for programmatic handling.

CodeStatusDescriptionResolution
AUTH_INVALID401Expired or malformed tokenRefresh via OAuth2 flow
SCOPE_DENIED403Insufficient permissionsRequest elevated scope or use service account
RATE_LIMITED429Exceeded requests per windowImplement exponential backoff
MESH_UNREACHABLE503Downstream subsidiary node offlineReroute via regional failover
🚨 Critical
If you encounter 500 or 503 errors persisting beyond 3 minutes, contact platform engineering via secure channel. Do not retry rapidly as this may trigger DDoS mitigation.
"