Quickstarts
Every quickstart ends with the same proof: a server sends a Fabrik request, receives a message ID, and has a safe way to observe the final outcome. Start with Node.js unless your application already has a preferred framework.
Choose your path
Section titled “Choose your path”Node.js & TypeScriptThe canonical path. Install the official SDK and send a managed message in sandbox.
Next.js App RouterKeep Fabrik in a Route Handler, protect secrets, and verify a webhook from raw request bytes.
CLI + typed definitionsGenerate a checked catalog of released message keys and variables for CI.
Before you begin
Section titled “Before you begin”You need:
- Node.js 22 or later.
- A Fabrik application and a
sk_test_secret key. - One released message definition if you follow the managed-message quickstart.
- A trusted server runtime. The SDK must not run in a browser, client component, or mobile bundle.
What success looks like
Section titled “What success looks like”- The request is accepted. The response contains a Fabrik resource ID and request metadata.
- The delivery is observable. Retrieve the resource or receive a signed webhook event.
- The retry is safe. Reusing the same idempotency key returns the original logical result instead of creating a duplicate send.
After the quickstart
Section titled “After the quickstart”Move from “it sent” to “we can operate it” with webhook verification, delivery reports, and the going-live checklist.