API

Read your Flitch data and write to input tables from your own applications over HTTPS.

The Flitch API lets an external application read the data in a space and write rows to its input tables. Plain HTTPS and JSON, no SDK required.

The API is in early access and is enabled per account. If you want access, email hello@flitch.io. Calls from an account that is not enabled return 403.

Base URL

https://app.flitch.io/api/v1

Every endpoint sits under the version prefix. A breaking change ships as /api/v2, and /api/v1 keeps working for at least 12 months after that.

Quick start

Create a key at Settings → API Keys, then confirm it works:

curl https://app.flitch.io/api/v1/me \
  -H "Authorization: Bearer flk_live_..."

The response names the key and the space it belongs to. From there, list what it can reach:

curl https://app.flitch.io/api/v1/datasets \
  -H "Authorization: Bearer flk_live_..."

Sections

Authentication

API keys, session tokens, scopes, and what a key can reach.

Endpoints

Every route, its parameters, and its response.

Errors and limits

Error codes, rate limits, and idempotent writes.

What it covers

You can	You cannot
List datasets a credential may reach	Create or upload datasets
Read rows from uploads and connection-backed datasets	Add or edit connections
Query a connection, including GeoJSON for spatial sources	Generate, edit, or publish dashboards
Insert, update, and delete input-table rows	Mint API keys

Datasets and connections are created in the Flitch UI. The API reads what is already there and writes to input tables.

Requests are answered with Access-Control-Allow-Origin: *, so a browser or mobile client can call the API directly. Preflight OPTIONS returns 204 and allows the Content-Type, Authorization, and Idempotency-Key headers.

No cookie, CSRF token, or referer is ever required. The bearer token is the only credential.