# Developer hub

> REST API, signed webhooks and an MCP server: three ways to connect WhatSetter to your CRM, your scripts and your AI assistants.

Source: https://docs.whatsetter.com/developers/

This section is for developers and technical integrations. If you want to use WhatSetter day to day (campaigns, conversations, meetings), go to the [dashboard guides](/getting-started/agent/).

## Three ways in

  
### REST API

    65 endpoints to read leads and conversations, import contacts, send messages through the anti-ban engine, drive campaigns, read and change your agents' prompts and knowledge, block numbers, read your tracked links and plan your Instagram posts.
    [Quickstart](/developers/quickstart/) · [Authentication](/developers/authentication/)
  
  
### Signed webhooks

    WhatSetter pushes events to your server the moment they happen: lead qualified, lead ruled out, number disconnected. Every delivery is signed with HMAC-SHA256.
    [Set up webhooks](/developers/webhooks/)
  
  
### MCP server

    66 tools for Claude, Cursor, VS Code, ChatGPT, Gemini CLI and Codex CLI. Your assistant reads your leads, imports contacts, or explains why an agent said something and corrects its prompt, from a chat.
    [Connect an assistant](/developers/mcp/)
  
  
### API reference

    One page per endpoint, generated from the OpenAPI 3.1 spec, with schemas, examples and a "Try it" console.
    [Open the reference](/api-reference/)
  

## Guides by resource

Each guide shows the same request in cURL, JavaScript and Python, the response you get, and the errors that matter for that endpoint.

  - [Leads](/developers/guides/leads/)
  - [Lists and import](/developers/guides/lists-import/)
  - [Campaigns](/developers/guides/campaigns/)
  - [Agent prompts](/developers/guides/prompts/)
  - [Knowledge bases](/developers/guides/knowledge/)
  - [Messages](/developers/guides/messages/)
  - [Conversations](/developers/guides/conversations/)
  - [Bookings](/developers/guides/bookings/)
  - [Groups](/developers/guides/groups/)
  - [Blocked contacts](/developers/guides/blocked-contacts/)
  - [Team](/developers/guides/team/)
  - [Tracked links](/developers/guides/links/)

## Principles

- **One key for everything.** The same `ws_live_…` key works for the REST API and the MCP server. Revoke it and both stop within a minute.
- **Scopes.** Every key carries permissions (`leads:read`, `messages:send`, `blocklist:manage` and so on). Grant each integration the minimum it needs. See [Authentication and permissions](/developers/authentication/).
- **The anti-ban cannot be bypassed.** The API applies the [same protections](/dashboard/anti-ban/) as the dashboard: no cold outreach through `POST /messages`, a daily quota per WhatsApp number, humanized sends.
- **One error envelope.** Every error is `{ "error": { "code": "…", "message": "…" } }` with a stable `code`. See [Errors, limits and idempotency](/developers/errors/).
- **Your workspace only.** A key sees its own workspace. An id that belongs to another workspace answers `404`, never `403`.

## By the numbers

| What | Count |
|---|---|
| REST endpoints | 65 |
| MCP tools | 66 |
| Scopes | 18, plus **Full access** |
| Webhook events | 5, of which 3 are emitted today |

## Related

- [Use these docs with AI assistants](/developers/ai-assistants/)
- [Errors, limits and idempotency](/developers/errors/)
- [MCP server](/developers/mcp/)
- [API reference](/api-reference/)
