Arizen Cloud REST API v1

Developer Documentation

Integrate Arizen Cloud hosting, server power actions, subscription lifecycle events, and billing telemetry directly into your Discord bots, deployment pipelines, and control panels.

Manage API Keys in Dashboard
Base URL: https://api.azcloud.site/api/v1
Code Examples

1. Authentication & API Keys

All API requests must be authenticated using a customer API key passed in the standard Authorization: Bearer <KEY> header or via the X-API-Key header. Secret keys begin with the az_live_ prefix.

curl -X GET "https://api.azcloud.site/api/v1/account" \
  -H "Authorization: Bearer az_live_example_secret_key" \
  -H "Accept: application/json"

2. Permission Scopes

ScopeDescriptionAssociated Endpoints
account:readView customer profile & API usage telemetryGET /account, GET /account/usage
services:readList hosting services, specs & utilizationGET /services, GET /services/:id, GET /servers/:id/utilization
servers:controlExecute power actions (start, stop, restart, kill)POST /servers/:id/power
orders:readView customer orders historyGET /orders, GET /orders/:id
invoices:readView invoices and transaction receiptsGET /invoices, GET /invoices/:id
webhooks:manageRegister, test, and remove webhook endpointsPOST/GET/DELETE /webhooks

3. Server Management & Power Actions

Send real-time power signals to your server instances. Signals must be one of: start, stop, restart, or kill. Requests verify customer ownership and prevent power actions on suspended services.

curl -X POST "https://api.azcloud.site/api/v1/servers/8b7e2a44/power" \
  -H "Authorization: Bearer az_live_example_secret_key" \
  -H "Content-Type: application/json" \
  -d '{"action": "restart"}'

4. Webhooks & Cryptographic Signature Verification

Outgoing webhook requests include the header X-Arizen-Signature: t=<timestamp>,v1=<signature>. To ensure authenticity and prevent replay attacks, calculate HMAC-SHA256 over <timestamp>.<raw_payload> using your secret and perform constant-time comparison.

# Webhooks arrive via HTTP POST from Arizen Cloud
# Signature header: X-Arizen-Signature: t=1690000000,v1=abc123hex...

5. Standard Response Format & Error Codes

All endpoints return a uniform JSON envelope containing success, data, and optional meta or error objects.

200 OK Response Envelope
{
  "success": true,
  "data": { ... },
  "meta": {
    "pagination": { "page": 1, "limit": 10, "total": 42 },
    "timestamp": "2026-11-16T12:00:00.000Z"
  }
}
Error Response Envelope
{
  "success": false,
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Too many requests. Please slow down."
  },
  "meta": {
    "timestamp": "2026-11-16T12:00:00.000Z"
  }
}