Lumika Connectors

Messaging infrastructure

Meet every client
where they already are.

One durable conversation layer for social, chat, text, voice and email—built to serve Lumika BDC today and independent client systems tomorrow.

Explore the API Service health
01conversation
InstagramWhatsApp MessengerTelegram TextVoice Email

01 / The layer

Connect once.
Build without channel logic.

Connectors owns provider authentication, webhooks, normalized conversations, delivery state and channel policy. Your product works with one versioned contract.

02 / Channels

A consistent shape, even when providers differ.

  • MetaMessenger · Instagram · WhatsApp
  • TelegramBot messaging
  • TwilioSMS/MMS · Voice
  • AWS SESDedicated email

Provider features are enabled only after the relevant account, consent and webhook checks pass.

03 / Public API

Safe defaults.
Explicit control.

Every client gets a scoped environment and an internally issued key. Mutations use idempotency keys; sending is checked again immediately before provider I/O.

Read the integration guide 
POST /v1/messages
Authorization: Bearer sk_live_…
Idempotency-Key: send_018…

{
  "conversation_id": "cnv_…",
  "text": "Hello from your product"
}

Hosted connection flow

Provider onboarding has one front door.

Client-specific setup can differ. The integration contract does not have to.

Review onboarding