v2.4.1 • Stable

API & Integration Platform

Access Aevum Zenth's unified developer ecosystem. Integrate with 400+ subsidiaries across energy, aerospace, healthcare, finance, logistics, and more through standardized RESTful endpoints, real-time webhooks, and language-specific SDKs.

Quick Start

Follow these steps to integrate with the Aevum Zenth API. All production endpoints require authentication and are served over HTTPS.

1. Generate an API Key

Navigate to /console/keys and create a new API key with the appropriate scope. Store it securely; do not commit it to version control.

2. Set the Base URL

⚠️ Environment Note Use https://api.sandbox.aevumzenth.com for development/testing and https://api.aevumzenth.com for production.

3. Make a Request

Bash
curl "https://api.aevumzenth.com/v2/divisions" \ -H "Authorization: Bearer AZENTH_API_KEY" \ -H "Content-Type: application/json" \ -H "X-AZ-App-Version: 1.0.0"

4. Parse the Response

JSON
{ "data": [ { "id": "div_energy_001", "name": "Aevum Energy & Power", "sector": "Renewables & Grid Infrastructure", "api_version": "v2.4", "status": "active" } ], "meta": { "request_id": "req_8f7a2b9c", "rate_limit_remaining": 482 } }

Authentication & Security

All API requests must be authenticated using Bearer tokens. Aevum Zenth supports OAuth 2.0 (Authorization Code & Client Credentials), API Keys, and IP Whitelisting for enterprise clients.

Method Use Case Scopes
POST /oauth/token Server-to-server integration read:division, write:logistics, admin:billing
POST /oauth/authorize User-authorized third-party apps read:profile, read:health-data
Header X-AZ-API-Key Legacy systems & internal microservices Division-specific scopes
🔒 Security Requirements Production environments enforce TLS 1.3, mutual TLS (mTLS) for financial/healthcare endpoints, and automatic token rotation every 90 days.

Core Endpoints

Explore the unified resource endpoints. Division-specific routes follow the pattern /v2/{division_slug}/{resource}.

Method Endpoint Description
GET /v2/divisions List all active divisions with metadata and API versioning
GET /v2/energy/grid/status?region=EU-WEST Real-time grid load, generation mix, and outage forecasts
POST /v2/logistics/tracking Register new shipment with multi-modal routing
GET /v2/health/patient-records/{id} HIPAA-compliant patient data retrieval (requires signed JWT)
POST /v2/finance/ledger/entries Submit transaction batch for reconciliation
PUT /v2/robotics/fleet/config Push OTA configuration updates to autonomous units

Client SDKs

Official SDKs provide type-safe clients, automatic retries, exponential backoff, and division-specific helpers.

pip install
pip install aevum-zenth-sdk
Python
import aevum_zenth # Initialize client client = aevum_zenth.Client( api_key="AZENTH_API_KEY", env="production" ) # Fetch real-time grid data response = client.energy.grid.status(region="APAC-SOUTH") print(response.data.load_mw)
npm install
npm install @aevum-zenth/sdk
TypeScript
import { AevumZenth } from "@aevum-zenth/sdk"; const client = new AevumZenth({ apiKey: "AZENTH_API_KEY", timeout: 5000 }); const tracking = await client.logistics.track( "SHMT-8829-APAC" ); console.log(tracking.location.lat);
go get
go get github.com/aevum-zenth/sdk-go/v2
Go
import "github.com/aevum-zenth/sdk-go/v2" client := aevum.New(sdk.WithKey("AZENTH_API_KEY")) ledger, err := client.Finance.Ledger.Submit(ctx, batch) if err != nil { log.Fatalf("Submission failed: %v", err) }
Maven
<dependency> <groupId>com.aevumzenth</groupId> <artifactId>az-sdk-java</artifactId> <version>2.4.1</version> </dependency>
Java
AevumClient client = AevumClient.builder() .apiKey("AZENTH_API_KEY") .region(Region.EU_WEST) .build(); GridStatus status = client.energy() .grid() .getCurrentStatus();

Webhooks & Events

Subscribe to real-time events across divisions. Aevum Zenth guarantees at-least-once delivery with configurable retry policies and HMAC-SHA256 signature verification.

POST /webhooks/subscribe
{ "url": "https://your-server.com/az-webhook", "events": ["logistics:shipment.arrived", "energy:grid.outage", "health:record.updated"], "secret": "whsec_8f7a2b9c...", "retry_policy": { "max_attempts": 5, "backoff": "exponential" } }
🔐 Verify Signatures Every payload includes an X-AZ-Signature header. Validate using your webhook secret before processing.

Rate Limits & Tiers

Plan Requests / min Burst Division Access
Developer 60 10 3 selected divisions
Professional 1,000 100 12 divisions + sandbox
Enterprise 10,000+ Custom Full catalog + dedicated support

Exceeding limits returns 429 Too Many Requests with Retry-After header. Enterprise clients can request dedicated API gateways.

Error Handling

All errors follow a consistent JSON structure. HTTP status codes indicate the category, while error_code provides machine-readable details.

Error Response
{ "error": { "status": 403, "code": "INSUFFICIENT_SCOPE", "message": "Token lacks 'write:logistics' scope.", "request_id": "req_8f7a2b9c", "docs_url": "https://docs.aevumzenth.com/errors/403" } }