REST API
REST API reference
Create contacts, send RCS messages, trigger flows, read analytics and subscribe to signed webhooks from your own systems. One brand-scoped API key, plain JSON over HTTPS.
- Bearer API keys, one per brand
- Contacts, messages, flows, analytics
- Signed webhooks with retries and replay
MCP server
MCP server
Connect Claude or any other MCP client to your Title account over OAuth 2.1 and work with contacts, flows, campaigns and analytics in natural language.
- 45 tools, 3 resources, 8 prompts
- OAuth 2.1 with PKCE, brand-scoped sessions
- Agent mode for Agent Connect keys
Agent Connect
Agent Connect
Connect your own AI agent to Title so it can have two-way RCS and SMS conversations with your customers. Receive messages by webhook or polling, reply with one API call.
- Webhook push or long-poll pull
- One send call, rich RCS replies
- Opt-outs, quiet hours and hand-off handled by Title
Getting an API key
API keys are issued per brand by the Title team. Email admin@titlebm.com with the brand you want to connect and what you are building, and we will send a key for that brand. Keys are shown once, so store them when they arrive.
Connecting an MCP client
No key needed. Add https://titlebm.com/api/mcp to your MCP client and sign in with your Title account when it asks. The session is locked to one brand. See the MCP server docs.
Plugging in your own agent
Agent Connect is turned on per brand. Create a connection in Settings, and your agent receives messages by webhook or polling and replies with one call. See the Agent Connect guide.