REST API · MCP · OpenAPI · self-serve keys

Flipbook API for agents and LLMs

Create, publish, share, update, delete, and embed high-quality flipbooks programmatically. Public reads are open by default; writes use self-serve API keys.

Quickstart

Anonymous public reads need no key. Creating, updating, deleting, and reading private flipbooks require Authorization: Bearer fk_live_....

curl https://urmuupgjgyacsuvmqyhc.supabase.co/functions/v1/api-v1/flipbooks

curl -X POST https://urmuupgjgyacsuvmqyhc.supabase.co/functions/v1/api-v1/flipbooks \
  -H "Authorization: Bearer fk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "title": "Q4 Report", "pages": ["https://cdn.example.com/p1.jpg"] }'

Core endpoints

  • GET /flipbooks — list public flipbooks with no key, or owner flipbooks with a key.
  • GET /flipbooks/{id_or_slug} — fetch a public flipbook by id or slug.
  • POST /flipbooks — create a flipbook from ordered page image URLs.
  • PATCH /flipbooks/{id} — update title, description, slug, or visibility.
  • DELETE /flipbooks/{id} — delete a flipbook owned by the API key user.
  • GET /flipbooks/{id}/embed — return the iframe embed URL and HTML snippet.

MCP server

Endpoint: https://urmuupgjgyacsuvmqyhc.supabase.co/functions/v1/mcp. Tools: create_flipbook, list_flipbooks, get_flipbook, update_flipbook, delete_flipbook, and get_embed_code.