Starport API

Unified RESTful interface for Aevum Zenth's cross-divisional infrastructure, logistics, and enterprise systems.

Base URL: https://starport.api.aevumzenth.com/v1

The Starport API provides programmatic access to real-time data across our 400+ subsidiaries. All endpoints return JSON responses and follow standard HTTP conventions. Authentication is required for all requests except health checks.

curl -X GET \"https://starport.api.aevumzenth.com/v1/systems\" \\
  -H \"Authorization: Bearer YOUR_ACCESS_TOKEN\" \\
  -H \"Accept: application/json\"

Authentication

🔐

Bearer Token Authentication

Include your API token in the Authorization header using the Bearer scheme. Tokens are scoped by division and endpoint access levels.

Header Format

Authorization: Bearer az_live_9f8e7d6c5b4a3210fedcba9876543210

Generate scoped keys from the Developer Console. Keys expire after 90 days and support IP whitelisting and endpoint scoping.

Rate Limits

Starport API uses sliding window rate limiting. Limits vary by tier and endpoint criticality.

1,000

Requests / minute (Standard)

10,000

Requests / minute (Enterprise)

50

Burst allowance

429

HTTP status on limit breach

Rate limit headers are included in every response: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Endpoints

GET /systems ▼

Retrieve a paginated list of all active infrastructure systems across divisions.

Parameter	Type	Description
`division`	string	Optional Filter by division (energy, aerospace, logistics...)
`status`	string	Optional Filter by operational status (active, maintenance, offline)
`limit`	integer	Optional Max results per page (default: 50, max: 200)

Response 200

{
  "data": [
    {
      "id": "sys_8f9e2a1b",
      "name": "Zenth Grid Hub Alpha",
      "division": "energy",
      "status": "active",
      "location": "Neo Geneva",
      "last_ping": "2026-01-15T08:42:11Z"
    }
  ],
  "meta": {
    "page": 1,
    "total": 142,
    "has_next": true
  }
}

POST /stations/register ▼

Register a new operational station or facility into the Starport tracking network.

Parameter	Type	Description
`name`	string	Required Official facility name
`coordinates`	object	Required { lat, lng } or orbital vector
`division`	string	Required Owning division slug

Request Body

{
  "name": "Orbital Platform Theta-7",
  "coordinates": { "lat": 46.2, "lng": 6.1 },
  "division": "aerospace"
}

GET /logistics/routes/:route_id ▼

Fetch real-time telemetry, ETA, and cargo manifest for a specific logistics route.

Response 200

{
  "route_id": "rt_99283a1c",
  "origin": "Singapore Hub",
  "destination": "Neo Geneva Central",
  "status": "in_transit",
  "eta": "2026-01-18T14:00:00Z",
  "cargo": {
    "weight_tons": 48.5,
    "items": 12,
    "classification": "industrial"
  }
}

PUT /finance/ledger/:transaction_id ▼

Update ledger status or add reconciliation notes to an existing financial transaction.

⚠ Requires finance:write scope and MFA confirmation for amounts > $50k.

Error Handling & Status Codes

Starport API uses standard HTTP status codes. Errors return a structured JSON payload with machine-readable codes.

200

Success

201

Created

400

Bad Request / Validation Error

401

Unauthorized / Invalid Token

403

Forbidden / Insufficient Scope

429

Rate Limit Exceeded

500

Internal Server Error

Error Response Format

{
  "error": {
    "code": "VALIDATION_FAILED",
    "message": "Field 'division' must be one of the approved slugs",
    "details": [{
      "field": "division",
      "value": "unknown_sector"
    }]
  }
}