Create a key
Open your dashboard and generate a personal API key. It is shown once — copy it.
Developer API
Build with the flipbook API
Create, update, and manage flipbooks programmatically. A small JSON REST API authenticated with personal keys.
Base URL: https://flipbook.apasaja.my/api/v1
Get started in 3 steps
Send it as Bearer
Add the header Authorization: Bearer <key> to every request.
Call the API
Create a flipbook from a PDF URL, then list, update, or delete it.
Authentication
Every request needs a personal API key sent as a Bearer token. Keys are tied to your account and respect your plan quotas. Generate and revoke them anytime from your dashboard.
Authorization: Bearer fbk_your_key_hereTreat keys like passwords. Only a hash is stored on our side — a lost key can be revoked, not recovered.
Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /api/v1/flipbooks | List your flipbooks |
| POST | /api/v1/flipbooks | Create a flipbook from a PDF URL |
| GET | /api/v1/flipbooks/{slug} | Get one flipbook + interactions |
| PATCH | /api/v1/flipbooks/{slug} | Update title, visibility, effect, flags |
| DELETE | /api/v1/flipbooks/{slug} | Delete a flipbook |
| GET | /api/v1/flipbooks/{slug}/stats | Views, pages, last viewed |
POST is accepted as an alias for PATCH and for {slug}/delete on hosts that block PATCH/DELETE.
Create a flipbook
Point the API at a public PDF URL. We download it, scan it for malware, count pages, generate a thumbnail, and publish.
curl -X POST "https://flipbook.apasaja.my/api/v1/flipbooks" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com/doc.pdf","title":"Annual Report 2025"}'Response 201:
{
"success": true,
"flipbook": {
"slug": "annual-report-2025-a1b2c3",
"title": "Annual Report 2025",
"pages": 24,
"url": "https://flipbook.apasaja.my/f/annual-report-2025-a1b2c3",
"embed_url": "https://flipbook.apasaja.my/embed/annual-report-2025-a1b2c3"
}
}