REST API

Everything you can do in the panel is a public API call. The web panel, MCP, and your scripts all use the same API.

Basics

export SAKA_TOKEN="saka_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Error format

Every error has the same shape, so it can be read by both people and AI agents. Field names and messages are in Indonesian, because that is what the API returns:

{
  "galat": {
    "kode": "server-terputus",
    "arti": "Server sedang tidak tersambung ke sakapanel.",
    "langkah": "Pastikan server hidup dan agent berjalan: `systemctl status saka-agent`. Aplikasi di server tetap jalan walau terputus."
  }
}

• kode (code): fixed, for programs to match on.
• arti (meaning): a short explanation.
• langkah (next step): what you should do (may be empty).
• detail: the raw technical message from the server, if any.

Common codes: belum-masuk (401), server-tidak-ada (404), server-terputus (409), perlu-konfirmasi (400), batas-server (403), isian-rusak (400), agent-sedang-diperbarui.

Response language

The panel is available in English (the default) and Indonesian, and the API follows the Accept-Language header. With Accept-Language: en, text meant for people (arti, langkah, task progress steps, and notes) is sent in English. Without the header, or with id, responses are in Indonesian. What never changes: the error kode, JSON field names, and values such as keadaan, so your code only needs to match on kode. MCP and Telegram messages stay in Indonesian.

curl -s https://app.saka.work/api/v1/server/<server-id> \
  -H "Authorization: Bearer $SAKA_TOKEN" \
  -H "Accept-Language: en"

Long-running tasks

Actions on a server are sent as tasks. If a task finishes quickly, the response contains the result right away. If not, the response is a 202 with the task and a note on how to follow it. Poll GET /tugas/{id} until keadaan becomes selesai or gagal. Creation of database clusters, load balancers, and sites is tracked through GET /database/{id}, GET /lb/{id}, and GET /situs/{id} (keadaan: dibuat, siap, or gagal).

Main endpoints

All paths below are relative to /api/v1.

Actions that delete or replace content (apps, clusters, load balancers, sites, restoring a site, moving a site now, releasing a server) reject the request with the code perlu-konfirmasi until the konfirmasi field contains the resource's name. Show the user what will be deleted first.

curl examples

List servers

curl -s https://app.saka.work/api/v1/server \
  -H "Authorization: Bearer $SAKA_TOKEN"

The response contains server: each server has an id (for example srv_…), nama, ip, os, terhubung, and status (CPU, RAM, disk, apps, readiness).

Create a database cluster

curl -s -X POST https://app.saka.work/api/v1/database \
  -H "Authorization: Bearer $SAKA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "mesin": "postgresql",
    "nama": "toko-produksi",
    "mode": "sinkron",
    "data": ["srv_aaaaaaaaaaaaaaaa", "srv_bbbbbbbbbbbbbbbb"],
    "saksi": "srv_cccccccccccccccc"
  }'

mesin: postgresql (default) or mariadb. mode: asinkron (default) or sinkron; MariaDB is always synchronous. The 202 response contains the cluster with keadaan: "dibuat". To follow it:

curl -s https://app.saka.work/api/v1/database/<id-klaster> \
  -H "Authorization: Bearer $SAKA_TOKEN"

Create a load balancer

curl -s -X POST https://app.saka.work/api/v1/lb \
  -H "Authorization: Bearer $SAKA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "nama": "toko-lb",
    "mode": "proxy",
    "domain": ["toko.contoh.id"],
    "penyeimbang": ["srv_1111111111111111", "srv_2222222222222222"],
    "tujuan": ["srv_3333333333333333", "srv_4444444444444444"],
    "cadangan": [],
    "port_tujuan": 8080,
    "kebijakan": "bergiliran",
    "sticky": false,
    "path_sehat": "/"
  }'

mode: proxy (default) or dns (no domain). kebijakan: bergiliran (round robin) or koneksi_tersedikit (least connections). port_tujuan defaults to 80. penyeimbang (balancers): 1 or 2 servers. Optional in proxy mode: izinkan (allow) and tolak (deny), lists of IPs/CIDRs for the firewall.

Run a fix, then follow the task

curl -s -X POST https://app.saka.work/api/v1/server/<id-server>/perbaiki \
  -H "Authorization: Bearer $SAKA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jenis": "swap"}'

curl -s https://app.saka.work/api/v1/tugas/<id-tugas> \
  -H "Authorization: Bearer $SAKA_TOKEN"

The response contains tugas (id, perintah, keadaan: antre, berjalan, selesai, or gagal, lewat: panel, api, or mcp), kemajuan (the step currently running), and hasil once it is finished.