With API Preview
A hero pairing a headline and CTA with a live API request and response preview. Built for developer tools and platforms aimed at technical buyers.
A hero pairing a headline and CTA with a live API request and response preview. Built for developer tools and platforms aimed at technical buyers.
Search blocks by description or jump to a page.
With API Preview is a centered hero with a live interactive code panel below the headline. At the top sits a badge, a large headline, a subtext line, and two buttons. Below those, a bordered card holds the full API playground: a header bar with three traffic-light dots and a language toggle (curl, Python, JavaScript), a two-column body split into a request pane on the left and a JSON response pane on the right, and a row of endpoint cards underneath each showing an HTTP method badge, the route path, and a short description. A three-column feature card row closes the section with icons for RESTful API, Rate Limiting, and Authentication.
The headline, subtext, and button labels are plain copy you can swap freely. The language tabs and the code samples in each pane are independent strings, so you can replace the demo endpoint and response object without affecting the layout. The endpoint list and the feature cards at the bottom are arrays you can extend or trim to match your actual surface area.
Reach for this block when the product is a platform or data API and you want technical buyers to understand the integration story before they click anything. For a healthcare scheduling product, for example, it lets a developer audience see how appointment or patient record endpoints work in their preferred language right on the landing page. It is more convincing than a code-only hero because the response pane confirms the shape of the data, and it is more focused than a full dashboard screenshot because every element points at the API contract.
A natural flow around it on a Marketing (Legacy) page:
Before
After
The obvious fit is your real API endpoints, with request bodies and responses drawn from your actual schema. A few other uses for the same frame:
Tip: keep the endpoint list to three or four rows so the card stays compact and the method badges remain readable without scrolling.