API overview

The Zanfia API lets you read and manage everything in your workspace programmatically — products, offers and prices, course content, communities, pages, clients, orders, and stats. Everything the Zanfia CLI does goes through this same API, so anything you see the CLI do, you can do with plain HTTP.

Two API surfaces

Both use the same bearer-token authentication and the same JSON conventions.

Your first request

Create an API key in the dashboard (see Authentication and API keys), then:

curl "https://europe-central2-mailingr-54736.cloudfunctions.net/api-v1/products" \
  -H "Authorization: Bearer YOUR_API_KEY"

The workspace is resolved from the key — you never pass a workspace id.

Conventions

• JSON in, JSON out. Send Content-Type: application/json on writes.
• Errors return a non-2xx status with a JSON body carrying a machine-readable reason — for example 404 with { "error": "lesson-not-found" }, or 403 with a code like insufficient-scope.
• Money is in minor units. 1999 means 19.99 in the given currency.
• Lists paginate with cursors. List endpoints accept limit and cursor parameters and return the next cursor with the page.
• Content is Markdown. Lesson bodies, posts, and comments are stored and returned as Markdown.

What to read next

• Authentication and API keys — create a key and scope it correctly.
• Endpoint reference — every route with schemas and code samples, one page per resource: Products, Offers & order bumps, Courses & quizzes, Media, Pages, Communities, Clients, Orders, stats & discounts.
• CLI quickstart — the same surface from your terminal, no HTTP needed.
• Connect AI clients via MCP — give Claude, Cursor, or ChatGPT direct access to your workspace.