Skip to main content
IntegrationsPricingBlogFree Tools
Developer API

Build Flipbooker Into Your Stack

A public REST API with API-key and OAuth 2.0 authentication gives you programmatic access to your flipbooks, leads, and reader analytics. Outbound webhooks push new views and leads straight to your own systems in real time.
Book a callView developer docsSee All Features
Terminal
$ # List your flipbooks
curl https://app.flipbooker.com/api/v1/books \
-H "Authorization: Bearer wsk_live_••••"
# 200 OK
{
"data": [{
"random_id": "aB3x",
"name": "Q3 Sales Deck",
"status": "publish",
"page_count": 24
}]
}
The Problem

Your Data Is Trapped in a Dashboard

Reader analytics and captured leads live inside Flipbooker, but your CRM, data warehouse, and internal tools live everywhere else. Without an API, your team is stuck copying data by hand and reacting to events hours after they happen.

Manual exports

Someone downloads a CSV every week and pastes leads into the CRM. Data is stale the moment it lands.

No real-time signal

A prospect opens your proposal and your sales team finds out tomorrow, not the moment it happens.

Disconnected tooling

Flipbook data never reaches your warehouse, scoring models, or automation, so it can't drive decisions.

Core Capabilities

Everything You Need to Integrate

A predictable REST API and event webhooks expose the data and actions your systems depend on.
  • Flipbooks
    List, retrieve, and manage flipbooks and their metadata programmatically, no manual exports required.
  • Leads
    Pull captured leads into your CRM or warehouse the moment they're collected, with full context.
  • Reader Analytics
    Query views, reading progress, read time, and link clicks per reader to power your own reporting.
  • Outbound Webhooks
    Subscribe to events and have Flipbooker notify your endpoints on new views and leads in real time.
  • REST API
    Resource-oriented endpoints, JSON payloads, and standard HTTP status codes that any client can call.
  • Secure by Default
    API keys for server-to-server calls and OAuth 2.0 for apps acting on behalf of a workspace.
Authentication

Two Ways to Authenticate

Use a workspace API key for your own backend integrations, or OAuth 2.0 when your app needs to act on behalf of another Flipbooker workspace.

API keys

Generate scoped keys for server-to-server requests. Rotate or revoke them at any time.

OAuth 2.0

The standard authorization-code flow lets users grant your app access without sharing credentials.

Scoped access

Grant each credential only the permissions it needs across flipbooks, leads, and analytics.

Authorization header
Authorization: Bearer wsk_live_••••••••
Webhooks

Get Notified the Moment It Happens

Subscribe to event topics and Flipbooker sends a signed HTTPS request to your endpoint whenever a reader opens a flipbook or a new lead is captured. No polling, no delay.
Webhook Deliveries
flipbook.viewed
Delivered to https://hooks.acme.com/flipbooker
200 OK
lead.created
Delivered to https://hooks.acme.com/flipbooker
200 OK
flipbook.viewed
Endpoint timed out, automatic retry queued
Retrying
Failed deliveries retry automatically with exponential backoff.
Event Subscriptions

Subscribe to the Events That Matter

Pick the topics your systems care about and let Flipbooker push the rest.
  • New views
    Fire automations the instant a reader opens a flipbook, so sales can follow up while interest is high.
  • New leads
    Route captured leads into your CRM, scoring model, or Slack channel the moment they're submitted.
  • Reliable delivery
    Signed payloads, automatic retries with backoff, and verifiable signatures keep your integration trustworthy.
Who It's For

Built for Teams That Integrate

Whether you're wiring up a single automation or a full data pipeline, the API meets you where you work.

Developers

A clean REST API, standard auth, and webhooks you can build against in an afternoon.

RevOps

Sync leads and engagement signals into your CRM and scoring models without manual exports.

Enterprise integration

OAuth 2.0, scoped credentials, and reliable event delivery for production-grade integrations.

The Developer API and webhooks are available on the Company and Enterprise plans.

Frequently Asked Questions

API Questions, Answered

Which plans include the Developer API?

The REST API, OAuth 2.0, and outbound webhooks are available on the Company and Enterprise plans.

How do I authenticate requests?

Use a workspace API key as a bearer token for server-to-server calls, or OAuth 2.0 when your app needs to act on behalf of a workspace. Each credential can be scoped to only the access it needs.

What can I access through the API?

You can programmatically work with your flipbooks, retrieve captured leads, and query reader analytics such as views, reading progress, read time, and link clicks.

How do webhooks work?

Subscribe an HTTPS endpoint to event topics like new views and new leads. Flipbooker sends a signed request to your endpoint whenever a matching event occurs, so you don't have to poll for changes.

What happens if my endpoint is down?

Failed webhook deliveries are retried automatically with exponential backoff, so a brief outage on your side won't cause you to miss events.

Where are the API docs?

Developer documentation is being finalized for public release. Book a call with our team and we'll walk you through endpoints, authentication, and webhooks for your use case.

Ready to Build With Flipbooker?

Book a call and we'll help you map the API and webhooks to your stack.

Start Your 14-Day Free Trial

$0 today. Cancel anytime. No risk.