NewUnlimited BYOH · $20/year · BYOH20
Discord

API & automation

Your tools.
Your workflow.

Check your apps, manage deployments and bring account information into the tools you already use. Connect a script to Caliber Node with a scoped API key.

Open API docs Make your first request
Caliber Node API
YOUR SCRIPT → YOUR ACCOUNT

A simple status check.

One request to list your apps.
Read access is all it needs.

GET/api/v1/apps
Read-only request

REST · JSON · Scoped API keys

Put it to work

Less checking by hand.

Start with one useful task. Add more permissions only when your integration needs them.

Monitor your apps

Pull app status into your own dashboard or scheduled checks.

apps:read

Manage deployments

Create app instances and manage their lifecycle from your scripts.

apps:write · apps:power

Keep account records

Read invoices, transactions and your balance for your own reporting.

billing:read

Quick start

Begin with a read-only call.

This example lists existing apps. It does not create, restart or change anything.

  1. Create a key

    Open Settings in the panel. Name your key and select apps:read. Save the token when it appears.

  2. Store it privately

    Set CALIBER_API_KEY in your shell or secret manager. Keep it on your server, out of browser code and public repositories.

  3. Make the request

    Run the cURL example. Use the returned app IDs for later requests and follow pagination when listing more results.

Shell · List your apps

# Set CALIBER_API_KEY in your shell or secret manager.
# Give this key the apps:read permission.
curl --fail-with-body \
  -H "Authorization: ApiKey $CALIBER_API_KEY" \
  'https://api.portal.calibernode.com/api/v1/apps?limit=10'

Requires cURL with --fail-with-body support. The variable must contain your real API key; no key is included in this example.

View the public route index

Build with confidence

A few things to get right.

Keep access narrow

Use a separate key for each integration. Revoke a key when you stop using it or suspect it has been exposed.

Wait for the result

App operations can take time. Poll for status, handle failures and set a timeout instead of assuming the app is ready.

Use the current reference

Check the panel’s API documentation for request fields and permissions. Use IDs returned by the API rather than guessing them.

Good to know

API questions, answered.

Connect your first script.

Start small, check the response, then build from there.

Open API docs