Getting Started
Welcome to the Aevum Zenth Developer Platform. This guide will help you initialize your integration with our unified API ecosystem, generate credentials, and make your first cross-divisional request.
While Aevum Zenth operates across 400+ subsidiaries, all developer interactions route through a single gateway (`api.aevumzenth.com`) with division-specific namespaces. No separate endpoints or legacy bridges required.
Prerequisites
- Active Enterprise Developer Account verified via the Aevum Console
- Access tier:
Standard,Pro, orEnterprise - Modern HTTP client or one of our supported SDKs
- Base URL:
https://api.aevumzenth.com
Quickstart
1. Create a Project & Generate Keys
Navigate to the Aevum Console, create a new integration project, and generate an API key. You'll receive a CLIENT_ID and CLIENT_SECRET. Store these securely; they will not be displayed again.
2. Install the SDK
We provide officially maintained clients for Python, Node.js, Go, and Java. Choose your environment:
npm install @aevumzenth/core@latest
pip install aevum-zenth
3. Initialize the Client
Configure your client with your credentials and target environment. Production traffic routes through prod.api.aevumzenth.com, while staging uses staging.api.aevumzenth.com.
import os
from aevum_zenth import AevumClient
client = AevumClient(
client_id=os.getenv("AEVUM_CLIENT_ID"),
client_secret=os.getenv("AEVUM_CLIENT_SECRET"),
environment="production"
)
# Verify connection
status = client.health.ping()
print(f"Gateway Status: {status['ok']} | Latency: {status['ms']}ms")
const { AevumClient } = require('@aevumzenth/core');
const client = new AevumClient({
clientId: process.env.AEVUM_CLIENT_ID,
clientSecret: process.env.AEVUM_CLIENT_SECRET,
environment: 'production'
});
client.health.ping()
.then(status => console.log(`Gateway: ${status.ok} | ${status.ms}ms`))
.catch(err => console.error('Connection failed:', err));
Making Your First Request
Once authenticated, you can query divisional data, submit telemetry, or trigger workflows. Requests use standard REST conventions with JSON payloads.
const response = await client.divisions.getStatus({
divisions: ['energy', 'aerospace', 'healthcare'],
region: 'us-east-1',
include_metrics: true
});
console.log(JSON.stringify(response, null, 2));
All divisional endpoints require a valid Bearer token. Tokens are automatically refreshed by the SDK. If using raw HTTP, implement OAuth2 client credentials flow with grant_type=client_credentials.
Understanding Division Routing
Aevum Zenth's gateway intelligently routes requests to divisional microservices based on the X-Aevum-Division header or SDK namespace. This enables:
- Cross-divisional queries without multiple auth handshakes
- Consistent rate limiting and quota management
- Unified error codes and webhook signatures
- Automatic fallback during regional maintenance