Search blocks by description or jump to a page.
A developer split with a headline, capability ticks, and a docs button beside an inverted code panel with file tabs and token styled lines.
The source for every Marketing block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
API and Webhooks Panel speaks to the developer who will actually wire your product into their stack. The left column makes the case in their language: a headline, a short lede, three capability ticks covering the REST API, webhooks, and SDKs, and an outline button to the docs. The right column shows rather than tells, with a code panel mockup that carries a tabbed header row, line numbers, a realistic webhook request in fake TypeScript, and a status footer confirming the call landed.
The panel is an inverted primary surface built entirely from theme tokens, and the syntax texture comes from spans at varied opacities rather than a highlighter library, so the block ships dependency free and stays legible in both light and dark mode. The code lives in a typed array of lines and tokens, so swapping in your own endpoints is a copy edit, not a refactor.
Reach for this block when developer buy in decides the deal. On a payments or data platform landing page it belongs right after the core product story, where the engineer evaluating you wants to see the request shape before they believe the marketing. It also pairs naturally with an integration directory, answering the visitor whose tool is missing with the message that they can build it themselves.
A natural flow around it on a Marketing Pro page:
Before
After
The obvious fit is your public API pitch. A few other ways to use the frame:
Tip: keep every code line under about sixty characters so the panel never scrolls sideways, and keep the snippet honest. Developers will read every line, so it should look like code you would actually ship.