Authentication & API Keys

Authenticate project-scoped server requests safely.

Base URL

https://facetime.trychert.com/api

Project API keys

ftk_… keys are bearer credentials for customer API access. Create them in Developer → Project API keys. Secrets are shown once, hashed at rest, and revocable at any time.

Use facetime:read for GET endpoints and facetime:write for mutations. Every request requires both headers:

Authorization: Bearer ftk_...
X-Chert-Project-Id: <your project UUID>

Worker credentials

ftw_… credentials identify internal Chert infrastructure for heartbeats and call reporting. They are never issued to customers; the prefix is documented only so you can recognize it.

Key hygiene

• Keep API keys server-side and out of browser bundles.
• For Hosted Sessions, send only the short-lived LiveKit participant token to the browser.
• Rotate by creating a replacement, migrating traffic, then revoking the old key.
• Webhook signing secrets are separate from API keys.