Authorization

Authentication in Callaba Engine is token-based. In practice, the dashboard gives you a ready-to-use JWT token for API requests, so most users do not need a separate sign-in flow before calling the API.

Open General settings in your Callaba dashboard and look for the API Token field inside the account settings block. That JWT token can be copied directly and sent in the x-access-token header of your API requests.

Where to find the token

1. Sign in to the dashboard as an account that is allowed to manage the instance.
2. Open General settings.
3. Scroll to the API Token row.
4. Use the Copy button next to the token.

This is the most practical starting point when you need to test requests from cURL, Postman, or an internal integration script.

How to send the token

Include the JWT token in the x-access-token header:

x-access-token: <your_api_token>

Practical notes

• Treat the JWT token as a secret. Do not paste it into public issue trackers, frontend bundles, or browser code that users can inspect.
• If you are building an internal tool, keep the token on the server side and proxy requests through your own backend.
• If access needs to be rotated, do it in the dashboard and update the systems that depend on it.

What to do next

Once you have the token, the easiest next step is usually to move into a concrete workflow such as creating an SRT server, configuring RTMP ingest, or building a player-facing delivery path.