Quickstart
Enable the Agent API, find your token, and make one authenticated call.
The Agent API is a local HTTP API that a running Meetily Pro instance exposes on http://127.0.0.1:8420. It is off by default and requires a Pro license.
In Settings > Integrations > Advanced, turn on the Automation API master switch and restart Meetily. Then, under Apps & scripts, turn on Allow for the auto-created loopback key so the CLI can connect (every key, including this one, starts "Not allowed yet"). See Enable & connect for a screenshot of every step.
Confirm the app is up:
curl -i http://127.0.0.1:8420/healthA 200 OK means the Automation API is up (no token needed for /health). If the call hangs or the connection is refused, the Automation API isn't enabled yet, or Meetily isn't running.
Locate your token. Meetily writes a loopback token to a file the first time the API starts:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/pro.meetily.ai/gateway-token |
| Windows | %APPDATA%\pro.meetily.ai\gateway-token |
| Linux | $XDG_DATA_HOME/pro.meetily.ai/gateway-token |
export TOKEN=$(cat ~/Library/Application\ Support/pro.meetily.ai/gateway-token)This file is loopback-only - only a caller on this machine can read it that way. An off-box caller uses the MEETILY_PRO_TOKEN environment variable instead (see Token resolution below).
Make one authenticated call.
meetily-pro whoamiNo token flag needed - the CLI reads the loopback token file automatically.
curl -H "Authorization: Bearer $TOKEN" http://127.0.0.1:8420/v1/whoami{"token_id":"<uuid>","scopes":["read"],"license_tier":"pro","server_version":"1.9.3"}Token resolution
A caller resolves its token in this order: an explicit --token-file flag, then the MEETILY_PRO_TOKEN environment variable, then the loopback token file above. There is no --token flag - it has been retired.
The built-in key is read-only
The token you just used only holds the read scope, which is why whoami above returns "scopes":["read"]. To record, write, or delete, create a scoped key under Settings > Integrations > Apps & scripts > Create key and turn on its Allow toggle - see Enable & connect.
Next steps
- CLI - the full command set.
- Events - what you can subscribe to.
- Meetily APIs - the canonical endpoint manifest.
Last updated on