FlipLetters HTTP API

FlipLetters API

The HTTP API is small and lives on app.flipletters.com. There is no general “create a board via REST” route — boards are flipcode text. HTTP is for cloud actions that spend a human's plan.

Machine-readable spec

/openapi.json — OpenAPI 3
/api/openapi.yaml
/llms.txt — agent summary
/mcp — FlipLetters MCP (hosted HTTP + stdio)

Auth

Authorization: Bearer <firebase-id-token>
Authorization: Bearer flk_<secret>

A signed-in human creates keys in Studio → Account → API keys & agents. Agents never self-register. Scopes: render, team, postiz. Drafting flipcode and local MCP tools need no key.

Endpoints that exist

GET

/api/render

Capability probe (no auth), or job status with ?jobId= (render scope)

POST

/api/render

Start a cloud MP4 under the caller's plan (render scope)

DELETE

/api/render?jobId=

Cancel a queued or in-flight job (render scope)

POST

/api/team

Team library: listTeams, create, join, share, listTemplates, leave, removeTemplate

GET/POST/DELETE

/api/keys

Mint, list, and revoke flk_ keys (Firebase session only — not API keys)

GET

/api/workspaces

List agency projects

GET

/api/workspaces/{id}/destinations

Postiz share accounts on a project

GET

/api/postiz/integrations

Channels on a Postiz destination

POST

/api/postiz/schedule

Upload an export and schedule / draft / post

Errors are JSON: error (string message), code, hint.

What is not an HTTP API

MCP is hosted at https://app.flipletters.com/api/mcp and local stdio — npx -y flipletters-mcp-server
flipcode is @flipletters/flipcode on npm
No public partner webhooks. Stripe and TikTok callbacks are internal Studio integrations.