Documentation — Jina Connect

Quickstart

Three ways to get from zero to first message in under 10 minutes. Pick whichever fits your stack.

Hosted Cloud

Self-Host with Docker

Clone the repo, run docker-compose up. API, workers, Postgres, Redis & web app come up locally.

MCP for AI Agents

Add the MCP server config to Claude Desktop / Cursor / Continue.dev. AI agents can send messages as native tools.

5-minute hosted quickstart

Once you have an API key, send your first WhatsApp message:

curl

# Send a WhatsApp template message
curl -X POST https://api.jinaconnect.com/wa/v1/messages/ \
  -H "Authorization: Bearer jc_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+919876543210",
    "template": "order_confirmation",
    "language": "en",
    "variables": ["Amit", "ORD-1729"]
  }'

Authentication

Jina Connect uses JWT-based authentication with API keys scoped per tenant. Each request includes the API key as a Bearer token.

💡 API key formats: Live keys start with jc_live_, sandbox keys start with jc_test_. Sandbox traffic does not bill against your plan.

For interactive sessions (dashboard, admin), the backend uses the POST /token/ endpoint to issue access & refresh tokens. See API Reference for the full auth flow.

Channels

Every channel ships as a Django app with its own adapters, templates, and webhook handlers. Five channels are live today; Email is on the roadmap.

💬

WhatsApp Live

Meta Cloud API direct + Gupshup BSP. Templates, broadcasts, two-way, media.

📞

Voice Live

5 HTTP providers + 12 SIP trunks. IVR compiler, recordings, transcription.

✈️

Telegram Live

Bot API + webhooks. Templates, broadcasts, contacts, two-way messaging.

📱

SMS Live

Twilio · MSG91 · Fast2SMS. Multi-provider routing with DLR webhooks.

🟢

RCS Live

Google RBM + Meta RCS. Rich cards, suggested replies, carousels.

📧

Email Coming Soon

Transactional + campaign email through unified flows.

Voice (new in v1.0)

Programmable voice with a unified API across 5 HTTP voice providers (Twilio, Plivo, Vonage, Telnyx, Exotel) and 12 SIP trunk profiles (Knowlarity, Servetel, MyOperator, Tata Tele, Airtel & 7 more).

What ships

IVR compiler with DTMF + speech-gather, transfer, record
S3-backed call recordings with retention sweep
Pluggable transcription: Deepgram, OpenAI Whisper, or provider-native STT
Local rate-card + CDR billing for cost reconciliation
TCPA-style time-of-day compliance windows
Cross-channel SMS fallback if call doesn't connect

Place an outbound call

curl -X POST https://api.jinaconnect.com/voice/api/calls/ \
  -H "Authorization: Bearer jc_live_..." \
  -d '{
    "to": "+919876543210",
    "from": "+918860302401",
    "template_id": "appointment_reminder",
    "record": true,
    "transcription_provider": "deepgram"
  }'

MCP Server for AI Agents

Jina Connect ships a Model Context Protocol server with 13 tools. AI agents (Claude Desktop, Cursor, Continue.dev, ChatGPT with custom GPTs) can call your messaging stack as native tools — no glue code, no custom adapters.

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "jina-connect": {
      "command": "npx",
      "args": ["-y", "@jina-connect/mcp-server"],
      "env": { "JINA_API_KEY": "jc_live_..." }
    }
  }
}

Restart your AI agent and the Jina Connect tools (send_whatsapp, list_broadcasts, get_analytics, etc.) appear automatically.

Self-Hosting

The entire core platform is open-source under AGPL v3. Run it on your own infrastructure with one Docker command — zero data leaves your network.

bash

git clone https://github.com/JINA-CODE-SYSTEMS/jina-connect-unified-cpaas
cd jina-connect-unified-cpaas
cp .env.example .env  # edit your secrets
docker-compose up -d

# → API · Workers · Postgres · Redis · Web app ready in <2 min

Required services: Postgres 14+, Redis 6+, S3-compatible object storage (for media + recordings). Everything else (Celery workers, Daphne for WebSockets, Caddy for TLS) is included in docker-compose.yml.

Webhooks

Every inbound event (incoming message, delivery status, read receipt, call event, transcription completed) fires a webhook to URLs you register per tenant. Signatures use HMAC-SHA256 with your shared secret.

Event types

message.inbound — user sent you a message
message.status — delivery / read / failed
call.completed — voice call ended
call.transcription — Deepgram / Whisper finished STT
broadcast.finished — broadcast batch complete
template.approved — Meta approved your template

Multi-Tenant

Every workspace is an isolated tenant with its own users, contacts, templates, API keys, and Razorpay wallet. Designed for agencies running 5–50 client WABAs from one deployment.

Per-tenant branding (custom domain, custom logo, custom email sender)
Per-tenant wallets with Razorpay top-ups + automatic invoicing
RBAC + scoped API keys + audit logs
White-label resell — set your own per-tenant pricing

See For Agencies → for the full agency playbook.

Get Help

Three channels for support, fastest first:

WhatsApp → +91 88603 02401 (typically <2h response)
GitHub Issues → file a bug or feature request
Email → hello@jinacode.systems

Everything you need to ship on Jina Connect