API reference website webflow
Cadence — API Reference on Webflow
API Reference — Cadence
An API reference is where a developer decides whether integration will take an afternoon or become a week of guesswork. The page had to explain authentication, nine endpoints, request parameters, response formats, access scopes, rate limits and errors without feeling like a wall of documentation.
How it was solved
The page opens with the entire API model in one sentence: one base URL, nine endpoints. The global and EU base URLs sit directly beneath it, so the first implementation decision is visible before the developer starts scrolling.
Authentication comes first. The page explains the difference between public and server keys, which actions each key can perform, how keys are scoped and rotated, and how the API version is pinned. A real request header shows the exact structure instead of describing it abstractly.
The reference is divided into two working groups.
Ingest covers sending an event, sending a batch and identifying a user. Every endpoint includes its HTTP method, path, permitted key type, field definitions and practical constraints. Request and response tabs keep examples in context, including accepted responses, queue status and timestamps.
Read covers saved funnels, cohorts and event exports. Parameters such as date range, breakdown and conversion window are shown beside a complete response, so a developer can understand both the request and the shape of the returned data without opening another page.
A persistent navigation column keeps Authentication, Ingest, Read, Rate limits and Errors accessible throughout the page. The active item changes with the current section, making a long technical reference easier to scan and revisit.
Rate limits are presented by endpoint group and plan rather than buried in prose. The error table follows the same principle: status, stable machine-readable code and the exact action required to recover.
Result
A complete API reference that takes a developer from the first bearer token to a production request without leaving the page. Authentication rules, endpoint scopes, payloads, responses, limits and failure states all use one consistent structure.
Design and development
Information architecture, technical content structure, interface design, responsive layouts and Webflow build — all done by me, from the navigation system to every endpoint and code example.
Need a similar developer platform?
I can design and build the complete developer experience — API reference, documentation, code examples, status pages and product marketing.
How this page was built in Webflow
The reference was built as a reusable documentation system in Webflow rather than a collection of independent sections.
Authentication, endpoint cards, parameter rows, request and response panels, rate-limit tables and error states share the same base components. Combo classes handle HTTP methods, key permissions, required fields and active states without duplicating the structure.
The left navigation remains visible on long pages and tracks the section currently being read. Endpoint layouts use fluid grids so parameter names, descriptions and code examples remain aligned across desktop, tablet and mobile.
Code panels use a separate visual layer with syntax colours, request and response tabs and fixed formatting. The result behaves like technical documentation while remaining fully designed and maintained inside Webflow.
API Reference Overview
This block introduces the Cadence API reference with one base URL and nine REST endpoints. It explains authentication using public and server keys, API versioning and safe key rotation. A sticky sidebar provides quick access to authentication, rate limits, errors, ingest and read operations. The first endpoint documents how to send an event, including required parameters, user identification, event properties, timestamps, idempotency and a complete API response example.
Rate Limits and Error Handling
This block explains how the API behaves under load and how developers should handle failures. Rate limits are organized by endpoint group and pricing plan, covering ingest requests, read operations and exports. It also documents the response headers used to track remaining capacity and reset times. The error table pairs each HTTP status with a stable machine-readable code and a clear recovery action, including invalid keys, insufficient permissions, oversized payloads, quarantined properties, rate limiting and regional failover.
