Seegnals for developers

Getting started

• QuickstartCreate an API token, add your first prospect with one request and receive your first webhook. Ten minutes, no SDK.
• AuthenticationBearer tokens created in the app, one per integration, revocable at any time. How the header looks and what a 401 means.
• Rate limits and errorsSixty requests a minute per token, one JSON error shape, and the complete list of status codes and messages the API returns.
• Pagination and filtersOne scheme for every list: limit, an opaque cursor and next_cursor. How ordering works, what a keyset cursor guarantees, and the two documented exceptions.

REST API

• ProspectsCreate a prospect, optionally enrol them in a campaign, list and read prospects with their activity columns, and update them by id. Fields, validation, PATCH semantics.
• SuppressionsExclude an email address or a whole domain from every campaign in the workspace, and list what is excluded, from your CRM, your unsubscribe page or a Zap.
• Subscriptions (REST Hooks)Subscribe a URL to one event type and unsubscribe it again. Built for Zapier-style REST Hooks and for wiring your own receiver without the Webhooks tab.
• CampaignsRead campaigns with progress, display status, settings, steps and Stats totals; list enrollments; enrol existing prospects; pause and resume a campaign from the outside.
• CompaniesRead companies with their account temperature, and one company card with people, campaigns and recent events. The same numbers as the Companies view in the app.
• RepliesRead classified inbox replies across all connected mailboxes, and correct a classification from the outside the same way the inbox menu does.
• OffersRead sent offers with their read status, visits, returns and total reading time, and one offer with every visit and the time spent per page.
• MailboxesRead the sending mailboxes of the workspace with status, daily limit, sent today and the SPF, DKIM and DMARC state of each domain. Never credentials.

Webhooks

• WebhooksOne signed JSON POST per event: sent, replied, clicked, bounced, unsubscribed. Payload shape, headers, retries and what to do on your side.
• Verifying signaturesEvery delivery is signed with HMAC-SHA256 over the timestamp and the raw body. Check it in a few lines, in Node, Python or anything with an HMAC library.
• ZapierConnect Seegnals to Zapier with Webhooks by Zapier in both directions: catch events as triggers, add prospects and suppressions as actions.

MCP

• MCP serverConnect Claude Code, Cursor or any MCP client to your Seegnals workspace with one URL and your API token. Tools, errors, limits and the exact client configs.

Reference

• Scope and roadmapWhat the API covers today, what it deliberately leaves out, and what is being added. Read this before you design an integration.
• ChangelogEvery change to the public API, the webhooks and the MCP server, newest first. If it is not here, it is not live.