API keys and automation

Use Settings → API keys to create a key for a script or integration. Give it a clear name and select only the permissions the task needs. Keep it in a secret store or environment variable, never in a public repository or browser script.

The full key is shown once. Copy it securely before leaving the page. Revoke a key you no longer use or suspect has been exposed.

First request

For a key with app read permission, this request lists apps without modifying them:

curl --fail-with-body   -H "Authorization: ApiKey $CALIBER_API_KEY"   "https://api.portal.calibernode.com/api/v1/apps?limit=10"

Set CALIBER_API_KEY in your local environment first. Do not paste the real value into documentation or support messages.

Build against the API reference

Open API Docs in the panel for the current endpoints, fields, pagination and permissions. Check response status codes and error bodies. A key’s scope does not grant access to another customer’s resources.

Avoid blind retries of creation, payment or deletion requests: a timed-out request may already have succeeded. Read back the current state before retrying a mutation. Use bounded retries for transient read failures.

Not every panel action is necessarily exposed as an API endpoint. Use the current reference rather than assuming a UI button has a matching route.