Skip to content
AppmakeDocs
Log inGet started
Kalle by Appmake API · Get started

Authentication and API keys

Every request is signed with a secret key from your workspace. One key works for both the Kalle by Appmake API and the Platform API.

Base URLhttps://api.kalle.build/v1AuthBearer kalle_sk_…VersionKalle-Version: 2026-11-01

Sending your key

Send the key in the Authorization header as a bearer token, and the API version in Kalle-Version. All requests use HTTPS against https://api.kalle.build/v1.

Headers
Authorization: Bearer kalle_sk_live_...
Kalle-Version: 2026-11-01
Content-Type: application/json
GET/v1/models
curl https://api.kalle.build/v1/models \
  -H "Authorization: Bearer $KALLE_API_KEY" \
  -H "Kalle-Version: 2026-11-01"
Open in Appmake

Creating and managing keys

Create keys in Appmake under Kalle API. A key belongs to a workspace, and its usage is billed to that workspace's prepaid balance. You can see when each key was last used.

  • Give each server or app its own key, so you can turn one off without touching the others.
  • Restrict a key to the scopes it needs: messages, files, browser, platform:read, platform:write.
  • Rotate a key by creating a new one, deploying it and then deleting the old one.

If a key leaks

Delete the key in Appmake straight away. Deleted keys stop working within seconds. If we find one of your keys in a public GitHub repository, we disable it and email the workspace owners.