REST GraphQL WebSockets

Data APIs & Integration Hub

Access Aevum Zenth's unified enterprise data pipeline. Stream real-time telemetry, energy grid metrics, financial market feeds, and cross-divisional IoT data through our globally distributed API edge network.

All endpoints are versioned via URL path (/v1/). Legacy /v0/ endpoints are deprecated and will sunset on Q4 2026.

Authentication

Aevum Zenth APIs support three authentication methods. Enterprise clients are required to use mTLS or OAuth 2.0.

                            
                            
                            
                        

# API Key Authentication
curl -X GET https://api.aevumzenth.com/v1/energy/grid-status \
  -H "Authorization: Bearer az_live_sk_8f9a..." \
  -H "X-AZ-Division: energy"
                    

const response = await fetch('https://api.aevumzenth.com/v1/energy/grid-status', {
  headers: {
    'Authorization': `Bearer ${AZ_API_KEY}`,
    'X-AZ-Division': 'energy'
  }
});
                    

import requests

response = requests.get(
    "https://api.aevumzenth.com/v1/energy/grid-status",
    headers={"Authorization": f"Bearer {AZ_API_KEY}"}
)
print(response.json())
                    

Header	Required	Description
`Authorization`	Yes	Bearer token or API key
`X-AZ-Division`	Yes	Target division scope (e.g., `energy`, `finance`)
`X-Request-ID`	Optional	Trace ID for debugging & support
`Idempotency-Key`	POST only	Prevents duplicate mutations

Energy & Grid Division

Real-time access to power generation metrics, grid stability indices, and renewable output telemetry across 28 national grids.

GET /v1/energy/grid-status

Retrieves real-time grid frequency, load distribution, and outage alerts for specified regions.

region (query) latency_ms

POST /v1/energy/load-forecast

Submits custom load models for AI-driven demand prediction. Returns confidence intervals and optimization suggestions.

IoT & Telemetry Ingestion

POST /v1/telemetry/ingest

High-throughput endpoint for industrial sensor data, fleet telemetry, and smart meter readings. Supports batch payloads up to 5MB.

                        Sample Payload
                        
                    

{
  "device_id": "az-sensor-8842-neo-geneva",
  "division": "manufacturing",
  "metrics": [
    { "type": "temp_c", "value": 42.8, "ts": 1718920400 },
    { "type": "rpm", "value": 2400, "ts": 1718920401 }
  ]
}
                    

Rate Limits & Tiers

API access is tiered based on contract scope. Enterprise and Conglomerate tiers include dedicated edge routing and priority support.

Tier	Requests/min	WebSocket Limits	Support
Developer	120	1 concurrent	Community / Docs
Scale	2,400	5 concurrent	Email / Priority
Enterprise	24,000	50 concurrent	Dedicated TAM
Conglomerate	Unlimited	Custom	24/7 Engineering

US-Eastapi-us-1.aevumzenth.com

EU-Westapi-eu-1.aevumzenth.com

APACapi-ap-1.aevumzenth.com (Elevated latency)

Official SDKs

Native client libraries with built-in retry logic, rate limit handling, and division scoping.

Python

pip install aevum-zenth-sdk

Node.js

npm install @aevumzenth/api

go get github.com/aevumzenth/go-sdk

Rust

cargo add aevum-zenth

Error Handling

Standard HTTP status codes are used. Detailed error payloads include machine-readable codes for automated handling.

Code	HTTP	Description
`AZ_AUTH_INVALID`	401	Missing or expired token
`AZ_DIVISION_BLOCKED`	403	Key lacks division scope
`AZ_RATE_LIMITED`	429	Exceeded tier quota
`AZ_PAYLOAD_EXCEEDED`	413	Request body too large
`AZ_INTERNAL`	500	Upstream division service error

Division-specific errors may include nested details arrays. Always inspect X-AZ-Trace-ID when filing support tickets.