Developer hub

This section is for developers and technical integrations. If you’re looking for how to use WhatSetter day to day (campaigns, conversations, meetings), head to the dashboard guides.

Three ways to plug into WhatSetter:

REST API

Read your leads and conversations, import contacts, send messages through the anti-ban engine, drive your campaigns. Quickstart →

Signed webhooks

Get notified in real time: lead qualified, message received, meeting booked, number disconnected. Verifiable HMAC signatures. Set up →

MCP server

Drive WhatSetter from Claude, Cursor or any AI agent that speaks the Model Context Protocol: 19 ready-made tools. Connect →

Full API reference

All 19 endpoints with schemas, examples and an interactive sandbox (OpenAPI 3.1). Open the reference ↗

API principles

• One key for everything: the same ws_live_… key works for the REST API and the MCP server. Revoked = everything cut, instantly.
• Precise permissions: every key carries scopes (read leads, send messages, manage webhooks…). Grant the minimum needed.
• Anti-ban can’t be bypassed. The API enforces the same protections as the dashboard: no cold outreach, shared daily quota, humanized sends.
• Predictable errors: a single error envelope { "error": { "code", "message" } } across the whole surface.