Authentication
The API uses Bearer token authentication. Every request must include your API key in the Authorization header.
Getting your API key
Each workspace gets an API key automatically on creation. Find yours in the dashboard under Settings → API Keys.
API keys look like this:
findclix_a1b2c3d4e5f6...Making requests
Include the key as a Bearer token in the Authorization header:
bash
curl -H "Authorization: Bearer findclix_a1b2c3d4e5f6..." \
"https://findclix.com/api/v1/media"TIP
The API key is tied to your workspace. All data returned is scoped to that workspace — you'll never see another workspace's media, creators, or categories.
OpenAPI spec
The full API spec is available at:
GET /api/v1/openapi.jsonNo auth required. Useful for generating client libraries or exploring the API surface.
bash
curl -s https://findclix.com/api/v1/openapi.json | jq .info.title
# "Findclix API"TIP
Wiring up an AI agent? Point it at llms.txt — an index of every docs page with links to per-page Markdown.
Rate limits
There are no hard rate limits currently, but excessive use may be throttled. If you need higher limits, contact us.