Aevum Zenth / Digital Systems / Documentation

Getting Started

Connect to the Zenth Digital Systems API to manage infrastructure, monitor node clusters, and stream real-time telemetry data across your enterprise environment.

ℹ️
Base URL: All API requests should be made to https://api.zenth.digital/v2

1. Authentication

All endpoints require authentication via Bearer token in the Authorization header. Tokens are issued per tenant and scoped to specific resource groups.

HTTP 
GET /v2/systems/status HTTP/1.1
Host: api.zenth.digital
Authorization: Bearer ZT_live_8x92j4k29s0d1f7g3h5m
Content-Type: application/json
X-Zenth-Version: 2024-08-15

2. System Status Check

Verify connectivity and retrieve the current operational state of your assigned digital infrastructure cluster.

JavaScript 
const checkStatus = async () => {
  const response = await fetch('https://api.zenth.digital/v2/systems/status', {
    headers: {
      'Authorization': `Bearer ${API_KEY}`,
      'Content-Type': 'application/json'
    }
  });

  if (!response.ok) throw new Error(`API Error: ${response.status}`);
  
  const data = await response.json();
  console.log(data); // Returns cluster health, latency, and node count
};

3. Response Format

All successful responses return a JSON object with standardized fields including metadata, pagination, and resource state.

JSON Response 
{
  "meta": {
    "request_id": "req_9f82jd29s0d1",
    "timestamp": "2026-01-15T14:32:08Z",
    "version": "v2.4.1"
  },
  "data": {
    "cluster_id": "cl_7x29dk0f",
    "status": "operational",
    "nodes_active": 24,
    "avg_latency_ms": 12,
    "uptime_percent": 99.998
  },
  "pagination": {
    "page": 1,
    "limit": 50,
    "total": 1
  }
}

4. Error Handling

The API uses standard HTTP status codes to indicate success or failure. Error responses include a machine-readable code and human-readable message.

HTTP Code Code ID Description Resolution
200 SYS_OK Request succeeded None required
401 AUTH_INVALID Missing or expired token Rotate API key via dashboard
429 RATE_LIMIT Too many requests Implement exponential backoff
500 SYS_INTERNAL Infrastructure fault Check status page, retry later
⚠️
Rate Limits: Standard tier allows 1,200 requests per minute. Enterprise tier scales dynamically based on cluster allocation. Exceeding limits returns 429 with a Retry-After header.
← Previous Introduction