API Documentation
Integrate with Aevum Zenth's unified platform. Access energy telemetry, aerospace telemetry, financial instruments, healthcare data, logistics tracking, and all 400 division APIs through a single gateway.
Introduction
The Aevum Zenth API provides programmatic access to our unified enterprise platform. Built on a microservices architecture, the API exposes endpoints across all 400+ subsidiaries through a consistent RESTful interface with GraphQL query support.
API Features
- RESTful endpoints with consistent JSON responses
- GraphQL query support at
/graphql - Real-time WebSocket streams for telemetry data
- SSE (Server-Sent Events) for webhook push notifications
- Batch operations for bulk resource management
- OAuth 2.0 / PKCE and API Key authentication
- Automatic API versioning via URL path
- Pagination, filtering, and full-text search
Content Negotiation
All endpoints accept and return application/json. The Accept and Content-Type headers should be set accordingly.
# Standard request headers Accept: application/json Content-Type: application/json X-API-Version: 2026-01-15 # Optional: API date versioning X-Request-ID: req_a8f3k29x # Optional: for tracing
Authentication
Aevum Zenth supports multiple authentication methods. Choose based on your integration pattern.
đ API Keys
Simple key-based auth for server-to-server integrations. Include in the Authorization header. Best for backend services and batch operations.
đĄī¸ OAuth 2.0
Full OAuth 2.0 with PKCE for user-facing apps. Supports Authorization Code, Client Credentials, and Refresh Token flows.
đ mTLS
Mutual TLS for highly secure division-to-division communication. Required for Healthcare and Capital Group APIs.
đĒ JWT Bearer
JWT tokens issued via our auth service. Suitable for short-lived sessions and microservice auth.
API Key Authentication
curl -X GET \ https://api.aevumzenth.global/v3/organizations/me \ -H