Zenix API

Base URL

https://api.zenix.net.tr/v1

All endpoints are relative to this address. Plain HTTP is rejected.

Authentication

The account owner creates keys in the customer panel under API keys, confirming with their password and two-factor code. The key is shown once; store it like a password and send it on every request:

Authorization: Bearer zxc_live_...

Never put the key in a URL. Requests without a valid key get 401; repeated failures from one address are rate limited. The account owner is emailed when a key is created or revoked, and can revoke a key at any time.

Scopes

A key only works for the scopes it was created with. Scopes and services cannot be changed: to change them, revoke the key and create a new one. The allowed IP addresses can be edited in the customer panel at any time.

Service and IP restrictions

A key can be limited to selected services: lists then contain only those services, and account-wide scopes (invoices, tickets, BGP) cannot be granted. A key can also be limited to IP addresses or CIDR blocks; requests from other addresses get 403 ip_not_allowed. Keys can expire after 30, 90 or 365 days, or never.

Rate limits

Per key: 120 read and 20 write requests per minute. All keys of an account together: 300 read and 40 write requests per minute. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; when a limit is exceeded you get 429 with Retry-After.

Server status, overview and power actions also share a capacity with other customers and may return 429 server_rate_limited. Status is cached for 10 seconds and the server overview for 60 seconds, so polling faster does not give fresher data.

Requests and responses

• Responses are JSON: successful responses have success, data and meta.request_id; errors have success false, error.code, error.message and sometimes error.details. Quote the request_id when contacting support.
• Lists accept limit (1-100, default 25) and offset, and return meta.pagination with limit, offset, total and has_more. Unknown or repeated query parameters are rejected with 422.
• Amounts and other decimals are strings, for example 24.00, never floating-point numbers. Amounts come with a separate currency field.
• Timestamps are ISO 8601 with an offset (Z for UTC; appointment times use +03:00). Calendar days are YYYY-MM-DD. Energy days and months are UTC.
• Field names are snake_case. Status values may gain new values within v1; treat unknown values gracefully.

{
  "success": true,
  "data": [ { "id": 123, "product_name": "VDS 4", "status": "active", "recurring_amount": "24.00", "currency": "USD" } ],
  "meta": {
    "request_id": "7f3c9a2e-…",
    "pagination": { "limit": 10, "offset": 0, "total": 1, "has_more": false }
  }
}

Retries and idempotency

Write endpoints accept an Idempotency-Key header (1-64 characters: letters, digits, '.', '_', ':' or '-'). Retrying with the same key within 24 hours returns the original response with Idempotent-Replayed: true instead of repeating the action. Reusing a key with a different body returns 422 idempotency_key_reused. After a timeout (504) the action may still complete: retry with the same key rather than a new one.

Endpoints

Examples

List the first ten services:

curl https://api.zenix.net.tr/v1/services?limit=10 \
  -H "Authorization: Bearer $ZENIX_API_KEY"

Restart a server, safe to retry:

curl -X POST https://api.zenix.net.tr/v1/services/123/server/power \
  -H "Authorization: Bearer $ZENIX_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: restart-123-20261020" \
  -d '{"action":"restart"}'

Errors

Every error has a stable machine-readable code. Messages are fixed English text and may change; build your logic on the code.

{
  "success": false,
  "error": { "code": "insufficient_scope", "message": "…", "details": { "required_scope": "servers:power" } },
  "meta": { "request_id": "7f3c9a2e-…" }
}

Versioning

Within v1, fields and enum values may be added, so ignore fields you do not know. Breaking changes are published under a new version path.