HowConduitworks.
Seven distinct, verifiable steps from service onboarding to message delivery inspection. Click any step to scrub the live architecture inspector.
Create a Client
Provision a dedicated client entry for your service (e.g. checkout-service or auth-service). Client isolation guarantees that keys, templates, and logs remain segregated.
Generate API Key
Conduit creates a cryptographically random live key. The plaintext key is revealed once for immediate developer copy; Conduit immediately hashes and stores only the salted bcrypt representation.
Configure Messaging Provider
Set the Base URL, Session ID, and API Token for your WhatsApp Business API panel. Test connectivity directly from the admin console to verify live session reachability.
Map Templates to Purposes
Sync approved WhatsApp templates directly from your panel. Create purpose mappings (such as 'otp' or 'order_confirmation') so applications don't need hardcoded template names.
Send Request Through Conduit
Your application sends a clean REST payload to /v1/send-template with its Bearer API key. Conduit authenticates the key, transforms the payload, and dispatches to the WhatsApp provider.
Receive & Route Webhook Events
Status receipts from WhatsApp are received by Conduit's webhook listener and routed strictly to the originating client, updating delivery records.
Inspect Activity & Audit Logs
Monitor operational throughput in the dashboard. Drill down into individual message logs to inspect provider responses, latency, and failure codes with privacy masking.
Create a Client
Provision a dedicated client entry for your service (e.g. checkout-service or auth-service). Client isolation guarantees that keys, templates, and logs remain segregated.
{
"client_name": "Checkout Microservice",
"client_slug": "checkout-service",
"environment": "production",
"isolation_mode": "STRICT_TENANT"
}