Build with the Salesmsg API and MCP server. This page links to everything you need: authentication, the API reference, integration guides, and our AI agent integration. Before you begin, you'll need a Salesmsg account and a Personal Access Token.
The Salesmsg Public API. v2.2 is current with 500+ endpoints. All responses return JSON.
Two supported methods. Each supports granular :read and :write scopes per resource — request only the scopes your integration needs.
Personal Access Tokens (PAT) — for single-account integrations, scripts, and internal automation. Tied to a user account. Good for development and automation when an app only needs to manage one Salesmsg account.
OAuth 2.0 — for apps that authenticate other Salesmsg users on their behalf and use the issued token to access Salesmsg's functionality.
For partners and ISVs shipping a Salesmsg integration.
Connect your Salesmsg account to Claude or any MCP-compatible AI agent.
Operational details, constraints, and compliance requirements for the Salesmsg API.
60 requests per minute, global. Exceeding the limit blocks all API calls for the next 60 seconds and returns HTTP 429.
API v2.2 is current with 500+ endpoints. v2.2 builds on v2.1 (200 endpoints), which fully replaced v1.0.
Live system status and incident history. Learn more ↗
If your organization operates under HIPAA and needs to access PHI via the API, a BAA with Salesmsg is required. Learn more ↗
Try the API without creating a Salesmsg account. Learn more ↗
When you need a real person or updates.