REST API

A REST API (Representational State Transfer Application Programming Interface) is a set of web service endpoints that use standard HTTP methods — GET, POST, PUT, PATCH, and DELETE — to create, read, update, and remove resources. Each resource is identified by a URL, and the server responds with structured data, typically JSON. REST APIs follow a stateless request-response pattern, meaning each call contains all the information the server needs to process it, with no reliance on previous requests. They are the most widely adopted approach for software applications to exchange data programmatically across the web.

For digital publishers, a REST API turns a flipbook platform from a standalone dashboard into a programmable building block that fits into larger workflows. It enables automation — uploading PDFs, creating flipbooks, pulling [analytics](/glossary/analytics-dashboard) data — without manual intervention. Teams that publish hundreds of documents save significant time by scripting repetitive tasks. A REST API also opens the door to integrations with CRMs, marketing platforms, and content management systems, making the publishing platform part of a connected toolchain rather than an isolated product.

FlipLink provides [API Access](/features/api-access) that lets developers programmatically create, update, list, and delete flipbooks and documents. You can upload PDFs, configure viewer settings, retrieve analytics data, and manage leads through authenticated API endpoints. The API integrates with the broader [Automation & Integrations](/features/automation-and-integrations) ecosystem, including [webhooks](/glossary/webhook) that push real-time events to your own systems. Authentication uses API keys tied to your account, and all requests and responses use JSON format. Rate limits are documented so you can build reliable automations that respect platform capacity.

REST APIs rely on a small set of conventions that make them predictable: - **Resources and URLs** — every entity (a flipbook, a lead, an analytics report) has a unique URL. For example, `/api/get/abc123` identifies a specific flipbook. - **HTTP methods map to actions** — GET reads, POST creates, PUT/PATCH updates, DELETE removes. The method tells the server what you want to do; the URL tells it which resource. - **Statelessness** — the server does not remember previous requests. Each call includes its own authentication token and parameters. This makes scaling straightforward because any server in a cluster can handle any request. - **Status codes** — the server responds with standard HTTP codes: 200 for success, 201 for created, 400 for bad request, 401 for unauthorized, 404 for not found, 429 for rate-limited. These codes let your automation handle errors gracefully. - **Pagination** — list endpoints return results in pages, with metadata indicating total count and links to the next page.

**"REST API and API are the same thing."** REST is one architectural style for APIs. Other styles include GraphQL, gRPC, and SOAP. When someone says "API" without qualification, they usually mean REST, but the terms are not interchangeable. **"REST APIs require JSON."** JSON is the most common format, but REST itself does not mandate a specific data format. Some APIs support XML or other formats via content negotiation headers. In practice, most modern REST APIs — including FlipLink's — use JSON exclusively. **"Stateless means the server forgets everything."** Stateless refers to individual requests, not to the platform as a whole. The server still stores your flipbooks, settings, and data in its database. Stateless means each API call must include its own authentication and context rather than relying on a server-side session.

**What is the difference between REST API and [webhook](/glossary/webhook)?** A REST API requires your application to initiate requests — you ask for data or send commands. A webhook works in the opposite direction: the server pushes events to your application when something happens (a new lead captured, a flipbook viewed). Many workflows use both: REST API for on-demand operations and webhooks for real-time notifications. **What is a RESTful API?** "RESTful" means an API follows REST principles: resource-based URLs, standard HTTP methods, stateless communication, and structured responses. The terms "REST API" and "RESTful API" are used interchangeably in practice. **Do I need programming skills to use a REST API?** Writing custom code gives you the most flexibility, but many no-code platforms like Zapier, Make, and n8n can interact with REST APIs through visual interfaces. FlipLink's [API Access](/features/api-access) works with both custom code and automation platforms.

A REST API is the standard interface for programmatic access to web services. For FlipLink users, it means any workflow that involves creating, managing, or analyzing publications can be automated, integrated, and scaled beyond what a dashboard alone can offer.