The API for Every Customer Channel
Your AI Connector is one API, an MCP server and webhooks for AI agents on every messaging channel: WhatsApp, WhatsApp Web, Instagram, Messenger, SMS, Telegram, email, web chat, LINE, Viber, iMessage, Skool, LinkedIn, TikTok and Discord, plus any channel through the custom channel API, and AI voice calls on WhatsApp and phone lines. Social publishing and Meta ads run on the same key.
https://api.youraiconnector.com/v1curl https://api.youraiconnector.com/v1/agents \ -H "X-API-Key: $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Front Desk", "scrape_urls": ["https://example.com"] }'
const res = await fetch("https://api.youraiconnector.com/v1/agents", { method: "POST", headers: { "X-API-Key": process.env.API_KEY, "Content-Type": "application/json", }, body: JSON.stringify({ name: "Front Desk", scrape_urls: ["https://example.com"], }),});const agent = await res.json();
import os, requests res = requests.post( "https://api.youraiconnector.com/v1/agents", headers={"X-API-Key": os.environ["API_KEY"]}, json={ "name": "Front Desk", "scrape_urls": ["https://example.com"], },)agent = res.json()
{
"success": true,
"agent_id": "ag7HkQ2ZpLxR3mNb",
"substrate_campaign_id": null,
"agent_generation_queued": true
}
One API, fifteen channels, plus AI voice calls
- WhatsApp Web
- Messenger
- SMS
- Telegram
- Web chat
- LINE
- Viber
- iMessage
- Skool
- TikTok
- Discord
- Voice calls
- Any channel via custom API
Products
Everything a Business Does with Its Customers, Behind One Key
Agents, conversations, contacts, bookings, broadcasts, social publishing and Meta ads are all live on the API today.
Liveon the API now
-
Live
AI Agents
Create an agent from instructions or your website. It answers, qualifies and hands a chat to a person when it should.
- POST
/agents
- POST
-
Live
Messaging on Fifteen Channels
Send and receive on every channel with the same calls, and route each channel to an agent.
- POST
/contacts/send - PUT
/entry-points/channel-defaults
- POST
-
Live
Contacts and CRM
Contacts, lists and tags, plus deals in pipelines and tasks for your team.
- GET
/contacts - POST
/deals - GET
/tasks
- GET
-
Live
Bookings
Agents offer open slots and book into the calendar inside the conversation.
- GET
/appointments
- GET
-
Live
Broadcasts and Templates
Send to a list, and create WhatsApp templates for messages outside the reply window.
- POST
/broadcasts - POST
/whatsapp-templates
- POST
-
Live
Automations
Multi-step flows that run when something happens on a contact or in a conversation.
-
Live
AI Voice Calls
The agent answers WhatsApp calls and phone calls, books while it talks and leaves the transcript in the chat.
- GET
/voice-calls - PUT
/voice-calls/lines/{phoneNumber}
- GET
-
Live
Knowledge Base
Questions and answers, website pages and files the agent answers from.
- POST
/faqs
- POST
-
Live
Webhooks
Every message and event pushed to your server, signed with HMAC SHA256.
- POST
/webhooks
- POST
-
Live
MCP Server
Claude, ChatGPT and your own agents get the same tools as the REST API.
MCP server -
Live
Multi-Account API
One account per customer,
sub_account_idon any call, scoped keys and signed webhooks that name the account.- POST
/subaccounts
- POST
-
Live
Social Publishing
Create, schedule and publish posts to major social networks, with AI drafts. The DMs a post starts go to the agent that already answers your channels.
Post from Claude, ChatGPT or your own agent through the MCP server.
Social media API -
Live
Meta Ads
Create and manage Meta ad campaigns from the same key.
AI voice calls
The Agent Picks Up the Phone Too
The same agent that answers your chats takes calls, with the same knowledge, rules and actions. Switch calls on per line and choose when the AI answers.
- WhatsApp calls
- On WhatsApp Business API numbers and WhatsApp Web numbers.
- Phone calls
- Normal calls to your own Twilio number.
- During the call
- Answers from your knowledge base, books or moves an appointment, tags the contact, alerts a person and runs your custom functions.
- After the call
- The transcript shows in the contact's chat, a link or confirmation the caller asked for follows in writing, and a Call ended automation trigger carries the summary.
- When it answers
- Always, outside the agent's active hours, or when nobody picks up after 10, 15, 20 or 30 seconds.
- Language
- The agent's language by default, and the caller's when they speak another one.
ExampleA call in the inbox, with a made up customer.
curl https://api.youraiconnector.com/v1/voice-calls/lines/+447700900100 \
-X PUT \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"enabled": true,
"channel": "whatsapp_api",
"agent_id": "ag7HkQ2ZpLxR3mNb",
"when": "no_answer",
"no_answer_seconds": 20,
"who": "everyone"
}'
Quickstart
From API Key to a Live WhatsApp Agent in Three Calls
Every request goes to https://api.youraiconnector.com/v1 with your key in the X-API-Key header. Authorization: Bearer works too.
-
1
Check Your Key
Confirm the key works and see when it was created. The full key is never returned in plain text.
GET /api-keys/currentcurl https://api.youraiconnector.com/v1/api-keys/current \ -H "X-API-Key: $API_KEY"Response200 OK{ "api_key_masked": "••••••••••••7Q2x", "api_key_retrievable": true, "created_at": "2026-11-02T09:14:00.000Z" } -
2
Create an Agent
Give it a name, a language, instructions and a goal. Pass
scrape_urlsinstead and it learns from your website.POST /agentscurl https://api.youraiconnector.com/v1/agents \ -X POST \ -H "X-API-Key: $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Front Desk", "language": "en", "instructions": "Answer questions and book appointments.", "goal": "Book a first appointment" }'Response201 Created{ "success": true, "agent_id": "ag7HkQ2ZpLxR3mNb", ... } -
3
Route a Channel to It
Make the agent the default for new WhatsApp conversations. Every other channel works the same way.
PUT /entry-points/channel-defaultscurl https://api.youraiconnector.com/v1/entry-points/channel-defaults \ -X PUT \ -H "X-API-Key: $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "channel": "whatsapp", "agent_id": "ag7HkQ2ZpLxR3mNb" }'Response200 OK{ "entry_point_id": "Xq81bTz0RkLm4Vw2" }
Webhooks
Every Message, Signed and Delivered to Your Server
Subscribe a URL with POST /webhooks and receive events as they happen. GET /webhooks/events lists every event you can subscribe to.
- X-Webhook-Signature
v1=<hex>, an HMAC-SHA256 of the timestamp and the raw body, keyed with your signing secret.- X-Webhook-Timestamp
- When the event was sent, in Unix seconds. Reject old ones to stop replays.
- X-Webhook-Delivery
- A unique id per delivery. Use it to drop duplicates.
- Retries
- Opt in per subscription. Check delivery health and re-enable a paused endpoint over the API.
{ "event": "new_message", "contact": { "id": "<contact-id>", "phone_number": "+15551234567", "first_name": "Jane", "last_name": "Smith", "is_bot_active": true }, "agent": { "id": "<agent-id>", "name": "Front Desk" }, "message": { "id": "<message-id>", "body": "Hi, are you open on Saturday?", "direction": "inbound", "status": "received", "created_at": "2026-07-30T17:27:06.000Z", "channel": "whatsapp_web", "media_url": null }}
import crypto from "node:crypto"; export function verify(headers, rawBody, secret) { const ts = headers["x-webhook-timestamp"]; const sig = headers["x-webhook-signature"].replace("v1=", ""); if (Math.abs(Date.now() / 1000 - Number(ts)) > 300) return false; const expected = crypto .createHmac("sha256", secret) .update(`${ts}.${rawBody}`) .digest("hex"); return sig.length === expected.length && crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected));}
import hashlib, hmac, time def verify(headers, raw_body: bytes, secret: str) -> bool: ts = headers["X-Webhook-Timestamp"] sig = headers["X-Webhook-Signature"].removeprefix("v1=") if abs(time.time() - int(ts)) > 300: return False expected = hmac.new( secret.encode(), f"{ts}.".encode() + raw_body, hashlib.sha256 ).hexdigest() return hmac.compare_digest(sig, expected)
/webhooksSubscribe a URL/webhooks/eventsEvents you can subscribe to/webhooks/{webhookId}/healthDelivery health/webhooks/{webhookId}/reenableRe-enable delivery$ claude mcp add --transport http your-ai-connector \
https://mcp.youraiconnector.com/mcp \
--header "X-API-Key: $API_KEY"
{ "mcpServers": { "your-ai-connector": { "type": "http", "url": "https://mcp.youraiconnector.com/mcp", "headers": { "X-API-Key": "YOUR_API_KEY" } } }}
Server URL https://mcp.youraiconnector.com/mcp
Sign in with your account, no key to paste
MCP server
Let Claude, ChatGPT or Your Own Agent Use It
The same API as tools over the Model Context Protocol. Point any MCP client at https://mcp.youraiconnector.com/mcp with your key, or add it as a custom connector in Claude or ChatGPT and sign in.
- Claude Code
- One
claude mcp addcommand with your key as a header. - Claude, ChatGPT
- Add a custom connector with the server URL and sign in.
- Your own agent
- Any client that speaks streamable HTTP, configured with the JSON on the left.
Keys and access
Keys You Can Safely Hand Out
Give each integration only what it needs, rotate it without downtime, and act on each customer's account with your own key.
curl -G https://api.youraiconnector.com/v1/agents \
-d sub_account_id=$SUB_ACCOUNT_ID \
-H "X-API-Key: $API_KEY"
Scoped API Keys
Limit a key to read only, to certain sections of the API, or to a list of accounts. A key scoped to one account cannot touch your data or another account's.
Key Rotation
Rotate a key whenever you need to, and revoke one that should no longer work.
One Account per Customer sub_account_id
Platforms and SaaS products create an account for each customer and pass
sub_account_idto build and manage its agents, channels and inbox. Ownership is checked on every request.Signed Webhooks
Every delivery carries a signature and a timestamp, so your server knows it came from us and is fresh.
Inbox
A Ready Inbox for Every Account
Build your own UI on the API, or use the ready inbox. Every channel in one place, bookings in the calendar, and a person can take over any chat while the agent steps back.
ExampleAn example account in the inbox, with made up customers.
FAQ
Questions About the API
What is Your AI Connector?
The API for every customer channel. One REST API, an MCP server and signed webhooks let you run AI agents and conversations on WhatsApp, WhatsApp Web, Instagram, Messenger, SMS, Telegram, email, web chat, LINE, Viber, iMessage, Skool, LinkedIn, TikTok and Discord, plus AI voice calls on WhatsApp and phone lines. Social publishing and Meta ads are live on the same key.
How do I create an AI agent over the API?
Call POST /agents with a name and your website in scrape_urls. The agent is built from your site, and PUT /entry-points/channel-defaults makes it answer new conversations on a channel.
Which channels does the API support?
WhatsApp, WhatsApp Web, Instagram, Messenger, SMS, Telegram, email, web chat, LINE, Viber, iMessage, Skool, LinkedIn, TikTok and Discord, all through the same endpoints, plus any other channel through the custom channel API. AI voice calls are live too: the agent answers WhatsApp calls and phone calls. WhatsApp API, Instagram DM API.
Can the AI agent answer phone calls?
Yes. The agent picks up WhatsApp calls on WhatsApp Business API and WhatsApp Web numbers, and phone calls to your own Twilio number, with the same knowledge, rules and actions it uses in chat. It can book an appointment while it talks, the transcript shows in the contact's chat, and a link or confirmation the caller asked for follows in writing. Turn calls on per line with PUT /voice-calls/lines/{phoneNumber}. AI voice calls.
Can Claude or ChatGPT use it?
Yes. The hosted MCP server gives Claude, ChatGPT and your own agents the same tools as the REST API, with an API key or by signing in. MCP server.
Can I run a separate account for each of my customers?
Yes. Create one account per customer with POST /subaccounts, pass sub_account_id on any call, hand out scoped keys, and receive signed webhooks that name the account. Multi-account API.
Does it post to social media?
Yes. Create, schedule and publish posts to major social networks, with AI drafts, from the API or from Claude, ChatGPT or your own agent through the MCP server. Meta ad campaigns run through the same key. Social media API.
How do I get access?
Access is opened by request. Tell us what you are building and we reply by email with a key.
Request access
Tell Us What You Are Building
API access is opened by hand for now. Send a few lines about your product and the channels you need, and we reply by email with a key.
- 01You write to us. What you are building, who it is for and which channels.
- 02We reply by email. With access, or with a question if we need one.
- 03You make your first call. The quickstart above runs as is.
