Leadspicker API and webhooks

Which route to take

Webhooks

A webhook sends an HTTP POST with a JSON payload to your URL whenever a chosen event happens on the lists and sequences you select.

1. Add a webhook

   Go to Settings → WebHooks and click Add new. Give it a name you will recognise later.

2. Set the target URL

   The address that receives the POST requests.

3. Choose the events

   Pick one or more events from the table below.

4. Choose the targets

   Select the lists and sequences that should trigger it, or leave the field empty to cover all of them.

5. Test it

   Test sends a sample event to the URL and shows the JSON payload Leadspicker will post for each event.

A sequence can also call a URL at a chosen point: the Custom action step posts a payload for each contact that reaches it, and its settings show a preview of that payload.

The REST API and API keys

The public REST API works with the same objects as the interface: lists, sequences, contacts, columns and more. Create a key under Settings → API Keys with Create new API key, name it after the place it will be used, and store it somewhere safe.

• Reference. Every endpoint, with its parameters and responses: API documentation.
• API changelog. Settings → API Changelog lists changes to endpoints, fields and behaviour, so you can check what moved before you update your code.
• One key per use. A separate key for each integration lets you delete one without breaking the others.

CLI and MCP: the route for agents

If the caller is an AI agent or you at a terminal, you do not need an API key at all. The CLI is the npm package @leadspicker/cli: it needs Node.js 22 or newer, signs in through the browser, and exposes every API endpoint as a command. Start with npx @leadspicker/cli login; details are in CLI.

The MCP server at https://app.leadspicker.com/mcp gives tools such as Claude Code, Cursor or Codex the same capabilities as tools they can call, again with a browser sign-in. See the MCP server.

n8n and other automation tools

n8n is the automation tool Leadspicker is most often wired to. Point a Leadspicker webhook at a webhook trigger in n8n to start a workflow on a reply or a new contact, and call the REST API from the workflow to add contacts, update columns or read results. Other automation platforms work the same way as long as they can receive a POST request and call a REST API; there is no dedicated Leadspicker app for them.

Bring your own AI provider keys

Under Settings → Custom AI Providers, Add provider API key connects your own key for a provider such as OpenAI or Anthropic. Every model under that provider then becomes available for AI columns, and assistant chats on those models run on your key instead of your credits.

• The key is stored encrypted, and can be shared with the organisation or kept private.
• In the model picker of an AI column, models on your own keys are grouped separately; they are billed by the provider, not in credits.
• Web search inside an AI column runs on Leadspicker's side, so it uses credits even when the model itself runs on your key.