Conduit centralizes API keys, provider configurations, templates, OTP flows, and operational message logs between your applications and messaging providers.
A controlled, inspectable pipeline from application request to verified delivery response. Scroll to scrub the live pipeline.
Distributed microservices, web apps, and backend workers make standardized requests to Conduit rather than maintaining provider-specific SDKs.
Conduit validates incoming client API keys using salted bcrypt comparison, verifies active permissions, and isolates tenant boundaries.
The request purpose is resolved to an approved WhatsApp template, variables are sanitized, and the payload is transformed for the provider.
Conduit's adapter layer abstracts provider specifics. Currently connects to the WhatsApp Business API panel, architected for future Meta direct adapters.
The provider dispatches the verified message session and returns execution telemetry and delivery receipt IDs back across the boundary.
Delivery receipts and status updates are recorded in client-isolated audit logs with masked phone numbers for privacy and immediate failure inspection.
Distributed microservices, web apps, and backend workers make standardized requests to Conduit rather than maintaining provider-specific SDKs.
POST /v1/send-template HTTP/1.1
Host: api.conduit.internal
Authorization: Bearer cnd_live_9b4e1837f4820a1c
Content-Type: application/json
{
"template_key": "auth_otp",
"phone": "+919876543210",
"variables": { "code": "849201" }
}Inspect real Conduit UI patterns: tenant isolation, template sync states, and structured audit logs.
Applications call a clean REST interface. Conduit handles bcrypt authentication, purpose-to-template mapping, provider-specific session management, and delivers structured receipts back to your service.
curl -X POST "https://api.conduit.internal/v1/send-template" \
-H "Authorization: Bearer cnd_live_9b4e1837f4820a1c" \
-H "Content-Type: application/json" \
-d '{
"template_key": "auth_otp",
"phone": "+919876543210",
"variables": {
"code": "849201",
"valid_minutes": "10"
}
}'{
"status": "success",
"message_id": "wamid.HBgLOTE4ODIzNDkxMDIw",
"provider_status": "SENT",
"latency_ms": 42
}Instant operational awareness. Drill into failed dispatches, monitor volume trends, and inspect payload headers.
Transparent, verifiable security safeguards protecting credentials, sessions, and client isolation.
Client API keys are hashed with salted bcrypt upon creation. Conduit never stores plaintext keys in databases.
Plaintext keys are revealed exactly once to the administrator upon generation and cannot be retrieved later.
Sensitive downstream WhatsApp panel session tokens are encrypted at rest and always masked in management surfaces.
All client contexts, API keys, templates, and message logs are strictly partitioned by tenant ID.
Incoming status callbacks are matched against dedicated client slugs to prevent cross-service receipt leaks.
Management console sessions are protected by signed JSON Web Tokens with strict expiration and password hashing.
How Conduit prevents database credential leaks while authenticating high-speed API requests.
Create clients, manage WhatsApp templates, and access unified message logs from one operational dashboard.