Application
One product inside your workspace. It owns its API keys, environments, message definitions, webhooks, activity, and delivery history. A workspace can hold several applications.
Platform model
Fabrik is a communications control plane for product teams operating in Ghana and Nigeria. Your server sends through one authenticated API; your team controls content, routes, sender identity, delivery evidence, and spend from the dashboard.
The model in one minute
Section titled “The model in one minute”Environment
Sandbox and live are isolated. The sk_test_ or sk_live_ prefix selects which one a request
uses.
Message
A direct request owns its content. A managed request addresses a released definition by a stable
key such as order.shipped.
Delivery
The accepted request, delivery attempts, terminal status, cost, and webhook history form one traceable record.
Choose a channel
Section titled “Choose a channel”| Channel | Best for | Runtime surface | Live prerequisite |
|---|---|---|---|
| SMS | OTPs, alerts, receipts, operational updates | fabric.sms or fabric.messages |
An active sender ID for each destination country |
| Receipts, product mail, account notices | fabric.email or fabric.messages |
A verified sending domain | |
| Approved-template notifications and conversations | fabric.whatsapp or fabric.messages |
WhatsApp provider and template configuration |
Direct resources are useful when your application owns the final payload. Managed messages are useful when product, operations, or compliance teams need to update approved content without a deploy.
One send, one operational loop
Section titled “One send, one operational loop”- Prepare. Validate the recipient, content, channel rules, consent, and an optional cost ceiling.
- Accept. Fabrik records the message and reserves the required sandbox allowance or wallet funds.
- Dispatch. The virtual sandbox path or live provider attempts delivery.
- Observe. Retrieve the resource or consume a signed webhook until it reaches a terminal state.
- Reconcile. Match the delivery ID, your business reference, the final cost, and the wallet ledger.
An HTTP success is not the same as handset or inbox delivery. Treat message.delivered,
message.undelivered, and message.failed as the terminal evidence for a send.
Build the integration around four rules
Section titled “Build the integration around four rules”- Keep keys server-side. The TypeScript SDK throws when constructed in a browser; never expose a secret key in client code or a mobile bundle.
- Make writes idempotent. Reuse the same key when retrying the same business action. Use a new key only when you intend to send again.
- Use webhooks for outcomes. Verify the raw body, persist the event ID, and make processing safe when the same event is delivered more than once.
- Treat money as exact. Costs and balances are integer minor units represented as strings, never JavaScript floating-point numbers.
Start in sandboxMake one verified server-side send.
Choose a send pathCompare direct and managed messaging.
Operate deliveryVerify webhooks and reconcile terminal outcomes.
Prepare for liveComplete identity, funding, consent, and provider setup.