For developers · Updated October 30, 2026
Authentication and API keys
Choose an integration key or a personal API token.
Integration keys
Organization owners and administrators with hosting access can create a key in Admin Center → Advanced → Integration. Configure the exact HTTPS origins allowed to embed meetings. Keys begin with fmi_ and are shown once.
Send the key from your server:
Authorization: Bearer YOUR_INTEGRATION_KEY
Verify the key with GET /v1/integration. Integration keys support the /v1/integration meeting endpoints. They do not grant access to personal recordings or general account management.
Personal API tokens
Personal API tokens begin with fmk_ and are managed in Settings → API tokens. Use them for account APIs that accept personal tokens. Access follows the account's permissions. Platform administration and support management require browser sessions.
Security and errors
Keep keys in server-side secret storage. Never place them in browser JavaScript, URLs, public documents, or support tickets. Rotate or revoke a compromised key. Check HTTP status codes and the JSON error and message fields. Common responses include 400 for invalid input, 401 for authentication failure, 403 for access restrictions, 404 for an unavailable resource, and 429 for rate limits.
Was this article helpful?
Sign in to save your feedback.