Welcome to Zenth Core API
Access our unified developer ecosystem powering 400+ subsidiaries across energy, aerospace, healthcare, finance, and advanced manufacturing. The Zenth Core API provides RESTful endpoints, WebSocket streams, and SDK bindings for rapid integration.
New to Zenth Core? Generate a test API key in the Sandbox Dashboard and start building in under 5 minutes.
Authentication
All API requests require authentication via API keys or OAuth 2.0. API keys should be passed in the Authorization header using the Bearer scheme.
GET /v3/divisions/energy/grid-metrics
Host: api.aevumzenth.com
Authorization: Bearer zk_live_8f3a2b9c1d4e5f6789012345
Content-Type: application/json
Token Scopes
Keys are scoped per division. Common scopes include read:metrics, write:commands, admin:webhooks. Request minimal scopes to maintain security compliance across multinational operations.
Core Endpoints
| Method | Endpoint | Description | Rate Limit |
|---|---|---|---|
| GET | /v3/divisions |
List all active subsidiaries & operational statuses | 120 req/min |
| GET | /v3/divisions/{id}/status |
Real-time operational health & latency metrics | 60 req/min |
| POST | /v3/commands/batch |
Execute cross-division automation workflows | 30 req/min |
| POST | /v3/webhooks/register |
Subscribe to divisional event streams | 10 req/min |
Client Libraries
Official SDKs abstract authentication, pagination, and retry logic. All packages are published under the @aevumzenth namespace.
import { ZenthClient } from '@aevumzenth/core';
const client = new ZenthClient({
apiKey: process.env.ZENTH_API_KEY,
environment: 'sandbox'
});
async function getGridMetrics() {
const data = await client.divisions.energy.getMetrics({
region: 'EU_WEST',
interval: '5m'
});
console.log(data.payload.active_nodes); // 14,892
}
Rate Limits & Best Practices
The Zenth Core API enforces sliding window rate limits to protect infrastructure across global nodes. Limits vary by endpoint and subscription tier.
- Standard Tier: 1,000 req/min aggregate
- Enterprise Tier: 10,000+ req/min with dedicated routing
- WebSocket Streams: 5 concurrent connections per key
Implement retry logic with jitter. Upon receiving 429 Too Many Requests, wait for the Retry-After header value before resuming requests.
Need Help?
Our engineering team monitors the Developer Forum for architectural guidance. For production incidents or SLA escalations, contact dev-support@aevumzenth.com or use the Priority Queue in your dashboard.