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.
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 -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 Key | az_live_sk_ | Full API Access | 90 days |
| Test Key | az_test_sk_ | Sandbox Environment | Never |
| Service Account | az_svc_ | Scoped Permissions | Configurable |
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.
{
"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
LAST_WRITE_WINS- Default for non-critical metadataVECTOR_CLOCK_MERGE- Recommended for financial & ledger dataMANUAL_REVIEW- Triggers compliance workflow on divergence
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_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.
| Language | Package | Repository | Latest |
|---|---|---|---|
| TypeScript/JS | @aevumzenth/core | npm / GitHub | 2.4.1 |
| Python | py-zenth | PyPI / GitHub | 2.3.8 |
| Go | github.com/aevumzenth/go-zenth | Go Modules | v2.4.0 |
Error Reference
Standardized HTTP status codes with machine-readable error objects. Always check the error.code field for programmatic handling.
| Code | Status | Description | Resolution |
|---|---|---|---|
AUTH_INVALID | 401 | Expired or malformed token | Refresh via OAuth2 flow |
SCOPE_DENIED | 403 | Insufficient permissions | Request elevated scope or use service account |
RATE_LIMITED | 429 | Exceeded requests per window | Implement exponential backoff |
MESH_UNREACHABLE | 503 | Downstream subsidiary node offline | Reroute via regional failover |
500 or 503 errors persisting beyond 3 minutes, contact platform engineering via secure channel. Do not retry rapidly as this may trigger DDoS mitigation.