I need to understand the product
Start with the platform model to see how applications, channels, delivery, and billing fit together.
Get started
Fabrik helps your team connect business events to customer communication, then see what happened and what it cost. You can start with a sandbox request before you configure a sender, provider, or wallet for live traffic.
Choose your starting point
Section titled “Choose your starting point”I need to send a message
Follow the Node.js quickstart for a safe sandbox send from a trusted server.
I need to prepare for launch
Follow the going-live checklist for sender IDs, domains, funding, consent, and webhooks.
The five things to know
Section titled “The five things to know”Application
One product inside your workspace. It owns its keys, environments, message definitions, webhooks, activity, and delivery history.
Environment
Sandbox and live are isolated. Your sk_test_ or sk_live_ key chooses the environment.
Channel
Send SMS, email, or WhatsApp through a direct resource or a managed definition.
Delivery
A send can be accepted before the provider confirms the final outcome. Follow the delivery to a terminal state.
Cost
Sandbox activity uses test capacity. Live sends reserve wallet funds and expose exact costs in minor units.
Decide how your team will manage content
Section titled “Decide how your team will manage content”| Choose this | When it fits | Example |
|---|---|---|
| Direct send | Engineering owns the final payload and deploy cycle | A service sends a one-off receipt with fabric.email.send() |
| Managed message | Product, operations, or compliance needs controlled copy without a deploy | A service sends order.shipped with fabric.messages.send() |
| Batch send | The application needs to send up to 100 SMS items in one request | A consented campaign or scheduled notification run |
The delivery model is the same across these paths: use an idempotency key for retriable writes, consume signed webhooks for outcomes, and reconcile the delivery with your business reference.
Make your first safe send
Section titled “Make your first safe send”- Create an application in the Fabrik dashboard. It owns the resources for this integration.
- Create a sandbox key and store it as
FABRIC_API_KEYin a server-side secret manager. - Choose a channel and send path. Use direct SMS, email, or WhatsApp, or publish a managed definition.
- Send from trusted server code. The SDK must never be bundled into a browser or mobile client.
- Inspect the result. Read the response, retrieve the delivery, or process the signed webhook.
Key prefixes are the environment switch
Section titled “Key prefixes are the environment switch”| Key | Environment | What it does |
|---|---|---|
sk_test_… |
Sandbox | Uses virtual delivery and test capacity; no live provider charge |
sk_live_… |
Live | Uses configured providers; requires the live setup for the channel |
The SDK derives the environment from the prefix and rejects any other secret-key format before a network request. Sandbox and live definitions, webhook endpoints, activity, and provider resources are deliberately separate.
Continue by outcome
Section titled “Continue by outcome”Send the first messageInstall the SDK and complete a sandbox send.
Understand the channelsCompare SMS, email, WhatsApp, direct sends, and managed messages.
Operate deliveryVerify webhooks, handle retries, and reconcile terminal states.
Go live deliberatelyPrepare identity, domains, funding, consent, and live routes.