Flikk

API overview

The public REST API. Authenticate with an API key and drive Flikk from code.

The public API lets you create flows, run them, and read results from code. Use it for scripts, CI, or an agent working on your behalf. The public surface lives under /api/*; every endpoint documented here sits behind that prefix.

Authentication

Every /api/* request carries an API key. The key is scoped to one organization, so it decides which workspace the call reads and writes. Create keys in your workspace settings and send the key with each request.

Pass the key in the Authorization header as a bearer token. To target a specific organization, add the x-org-slug header; without it, the call resolves to your first organization.

curl https://api.flikk.dev/api/flows \
  -H "Authorization: Bearer flk_your_key_here" \
  -H "x-org-slug: your-org"

That call returns the flows in the target organization. The same two headers authenticate every other endpoint.

Keys are secrets. Treat a flk_* value like a password. Store it in an environment variable, never in a flow definition or a committed file.

Reference

Every endpoint, request shape, and response lives in the interactive API reference, where you can try calls in the browser and copy working snippets.

On this page