Flikly Developers
Getting started

Authentication

Every Developer API request must include your API key as a Bearer token. Keys are created in the Developer Portal — not via API-key-authenticated endpoints.

Bearer header

Authorization: Bearer flk_live_<prefix>_<secret>

# Example request
curl -s "https://api.flikly.ai/api/v1/developer/me" \
  -H "Authorization: Bearer flk_live_YOUR_PREFIX_YOUR_SECRET"

Live vs test keys

  • flk_live_… — production usage; charges credits and counts toward rate limits.
  • flk_test_… — separate key prefix for non-production integrations (select environment when creating a key in the portal). Test keys still require Team/Custom entitlement and use the same credit billing and job pipelines as live keys — they are not a billing sandbox.

Base URL

Use https://api.flikly.ai/api/v1/developer for all server-to-server calls. For local development, set your API base URL in your environment configuration.

Plan eligibility

Developer API v1 requires an active Team or Custom subscription. Free, Creator, and Pro plans do not include API access. Pro Limited API is not available in v1.

Security requirements

  • Never embed API keys in browser JavaScript, mobile apps, or public repositories.
  • Store keys in a secrets manager or environment variables on your server.
  • Rotate keys from the portal if a key may have leaked; revoke old keys immediately.
  • Use webhooks or server-side polling — do not expose keys to clients for job status.

Portal sign-in

The Developer Portal at developers.flikly.ai uses the main Flikly Clerk application (separate from flikly.ai). Portal routes under /api/v1/developer/portal/* use Clerk session auth for dashboards — not API keys.

See also: API Keys, Errors.