Voor AI-agents
MCP-server van SendHQ
Give an AI agent full, safe control of one SendHQ workspace: send and receive email, verify domains, publish templates, and investigate deliverability through 142 strictly typed tools. Written for agents first; humans welcome.
curl -fsSL https://downloads.sendhq.cc/install.sh | sh
claude mcp add sendhq --env SENDHQ_API_KEY=re_your_key -- sendhq mcpWat deze server is
The SendHQ MCP server lets an AI agent operate one SendHQ workspace through the Model Context Protocol: send email (single, batch, templated, replies, attachments, idempotent retries), read and search sent and received mail (subjects, bodies, and attachment names) and its delivery events, organize mail into labels with auto-filing rules, manage drafts and private attachments, author and publish hosted templates, add and verify domains and their DNS, set up inbound receiving and inbound addresses, inspect deliverability, bounces, complaints, and suppressions, run newsletters (consented contacts with tags and custom fields, segments, lists with signup forms, welcome emails, and newsletter sites, and broadcasts with pre-send checks, test sends, scheduling, and bot-filtered open and click reports), and read account usage, billing state, analytics, and API-key metadata.
Het is een lokale stdio-server die is ingebouwd in de sendhq CLI-binary. Je MCP-client start sendhq mcp als childproces en communiceert via JSON-RPC over stdin/stdout. Elke toolcall wordt één gedocumenteerd request naar de SendHQ REST API op https://sendhq.cc/api/v1, geauthenticeerd met de API-sleutel van je workspace. De MCP-server heeft dus precies de rechten van die sleutel en niet meer.
- 142 tools in 10 groups, generated from one catalog that is also published as tools.json.
- Strikte JSON Schemas: onbekende argumenten, verkeerde types en ontbrekende verplichte velden worden lokaal geweigerd voordat er iets bij SendHQ aankomt.
- Gestructureerde fouten met een stabiele
code, de HTTP-status, eenexplanation, een concreteremedyen of opnieuw proberen zin heeft. - Elke tool die echte e-mail verstuurt of data vernietigt, zegt dat in de eerste woorden van de beschrijving en heeft MCP-veiligheidsannotaties.
- De modus
--read-onlyverbergt alle tools die verzenden of iets wijzigen. - Er wordt niets gelogd. stdout bevat alleen protocolberichten; de API-sleutel en berichtinhoud komen nooit in een log terecht.
https://sendhq.cc/api/mcp (prijzen en docs opzoeken, geen toegang tot je account). De server op deze pagina is de volledige server met toegang tot je account; die draait lokaal of als de gehoste connector hieronder.Use SendHQ in Claude, ChatGPT and Grok
Geen installatie nodig: SendHQ draait deze server ook als gehoste connector op https://mcp.sendhq.cc/mcp, met dezelfde tools. Je logt in met je SendHQ-account in plaats van een sleutel te plakken.
Claude
- Open Settings → Connectors en zoek SendHQ in de directory, of kies Add custom connector en plak
https://mcp.sendhq.cc/mcp. - Klik op Connect, log in bij SendHQ, controleer de toegang en klik op Allow.
- Vraag Claude om je inbox te controleren, een e-mail vanaf je geverifieerde domein te versturen of een bounce uit te leggen.
ChatGPT
- Open Settings → Security and login and turn on Developer mode.
- Go to chatgpt.com/plugins, click Create MCP app, name it SendHQ and enter
https://mcp.sendhq.cc/mcp. - Sign in to SendHQ and click Allow, then pick SendHQ from the tools menu in a new chat.
Grok
- Go to grok.com/connectors, click New Connector, then Custom.
- Enter
https://mcp.sendhq.cc/mcp, sign in to SendHQ and click Allow.
Muse by Meta
In Muse, open Connectors and search for SendHQ. Click Connect, sign in to SendHQ and click Allow.
Goedkeuring en verbinding verbreken
- The
request_featuretool sends a feature request to the SendHQ team with your account details, so we can follow up by email. - Tools die echte e-mail versturen of data verwijderen, zijn als zodanig gelabeld. Of de assistent je eerst om toestemming vraagt, stel je per tool in de assistent in: kies in Claude voor die tools Needs approval onder Settings → Connectors → SendHQ.
- De connector krijgt een eigen API-sleutel, genoemd naar de assistent (bijvoorbeeld “Claude (AI connector)”). Verwijder die onder API Keys om de verbinding direct te verbreken.
- De connector kan geen API-sleutels aanmaken of intrekken en de facturering niet wijzigen. Bijlagen worden als base64 verstuurd en teruggegeven; er is geen toegang tot lokale bestanden.
- Sending requires an active subscription. There is no free allowance, including mail to the account owner.
Vragen: postmaster@sendhq.cc. Privacy: sendhq.cc/privacy.
Installeren
Installeer de sendhq-binary (Linux, macOS en Windows op x86-64 en arm64). Het installatieprogramma controleert de checksum van de release en zet de binary standaard in ~/.local/bin.
curl -fsSL https://downloads.sendhq.cc/install.sh | shirm https://downloads.sendhq.cc/install.ps1 | iexsendhq version
SENDHQ_API_KEY=re_your_key sendhq doctorMaak een API-sleutel aan in het dashboard op https://sendhq.cc/app#/keys. De MCP-server kan geen sleutels aanmaken. Het enige commando dat de server start is:
SENDHQ_API_KEY=re_your_key sendhq mcpNormaal start je dit nooit handmatig: de MCP-client doet dat. Als je het in een terminal uitvoert, wacht het op JSON-RPC via stdin.
Je client configureren
Claude Code
claude mcp add sendhq --env SENDHQ_API_KEY=re_your_key -- sendhq mcp
# read-only variant
claude mcp add sendhq-readonly --env SENDHQ_API_KEY=re_your_key -- sendhq mcp --read-onlyVoeg --scope user toe om de server in elk project beschikbaar te maken, of --scope project om hem naar de .mcp.json van het project te schrijven. Verwijs in een gedeelde .mcp.json naar de sleutel uit de omgeving in plaats van hem te committen; Claude Code expandeert ${VAR} in .mcp.json.
{
"mcpServers": {
"sendhq": {
"command": "sendhq",
"args": [
"mcp"
],
"env": {
"SENDHQ_API_KEY": "${SENDHQ_API_KEY}"
}
}
}
}OpenAI Codex
[mcp_servers.sendhq]
command = "sendhq"
args = ["mcp"]
env = { SENDHQ_API_KEY = "re_your_key" }Of via de commandline: codex mcp add sendhq --env SENDHQ_API_KEY=re_your_key -- sendhq mcp.
Claude Desktop
Bewerk claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\) en herstart de app. Desktopapps nemen het PATH van je shell niet over, dus gebruik het absolute pad van de binary (which sendhq).
{
"mcpServers": {
"sendhq": {
"command": "/Users/you/.local/bin/sendhq",
"args": [
"mcp"
],
"env": {
"SENDHQ_API_KEY": "re_your_key"
}
}
}
}Elke andere MCP-client
Configureer een stdio-server met het commando sendhq, de argumenten ["mcp"] (optioneel "--read-only") en de omgevingsvariabelen hieronder. De server ondersteunt de MCP-protocolversies 2024-11-05, 2025-03-26, 2025-06-18 en 2025-11-25, en implementeert initialize, ping, tools/list en tools/call. Toolresultaten bevatten zowel een JSON-tekstblok als structuredContent.
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"1"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_service_health","arguments":{}}}Er is geen gehost HTTP-transport voor de server met toegang tot je account. Een remote MCP-endpoint met schrijfrechten zou OAuth per gebruiker vereisen, en dat biedt SendHQ niet; de lokale binary houdt de sleutel op de machine waar hij al staat.
Omgeving en flags
| Variabele of flag | Verplicht | Betekenis |
|---|---|---|
SENDHQ_API_KEY | ja | API-sleutel van de workspace (re_…). Elke tool behalve get_service_health heeft hem nodig. Zonder sleutel start de server wel, maar elke call geeft een gestructureerde auth_error terug die uitlegt hoe je het oplost. |
SENDHQ_API_BASE_URL | nee | Base-URL van de API. Standaard https://sendhq.cc/api/v1. Gebruik dit alleen voor een lokale of staging-omgeving. SENDHQ_BASE_URL wordt geaccepteerd als oudere alias. |
SENDHQ_MCP_READ_ONLY | nee | 1, true of yes werkt hetzelfde als --read-only. |
--read-only | nee | Stelt alleen tools beschikbaar die geen e-mail versturen en niets wijzigen. Verborgen tools worden ook geweigerd als ze bij naam worden aangeroepen. |
SENDHQ_PROFILE / --profile | nee | Gebruik een sleutel die sendhq auth login in de keyring van het besturingssysteem heeft opgeslagen, in plaats van SENDHQ_API_KEY. Zijn beide aanwezig, dan heeft de omgevingsvariabele voorrang. |
De sleutel wordt alleen als Authorization: Bearer-header naar de geconfigureerde base-URL gestuurd. Hij wordt nooit afgedrukt, gelogd, herhaald in foutmeldingen of opgenomen in toolresultaten.
Veiligheidsmodel voor agents
- Sends real email.
send_email,send_batch,send_template_test,send_broadcast,send_broadcast_test,schedule_broadcast(at the scheduled time), andsend_broadcast_to_moredeliver mail to real people and consume delivery credits. Their descriptions start withSENDS REAL EMAIL. Call them only when the user explicitly asked for that specific message to be sent, with the recipients, sender, and content confirmed. - Destructive.
delete_email,delete_draft,delete_attachment,delete_domain,delete_inbox,remove_suppression, the campaign deletes (delete_contact,delete_list,remove_list_contact,delete_broadcast,cancel_broadcast,delete_segment,delete_contact_field), andbulk_update_contactsare markeddestructiveHint: trueand their descriptions start withDESTRUCTIVE. Confirm with the user first.remove_suppressionweakens a safety block and is appropriate only when a human confirms the address works again. - Wijzigt de status. Concepten, templates, domeinen en inboxen aanmaken of bijwerken, templates publiceren en verificatie starten wijzigt de workspace, maar verstuurt geen e-mail.
- Alleen-lezen. Al het andere is
readOnlyHint: trueen kun je vrij aanroepen. - Deze server wijzigt nooit DNS.
add_domaingeeft records terug die een mens moet publiceren;get_domain_connect_linkgeeft een toestemmings-URL terug die iemand moet openen en bij de DNS-provider moet goedkeuren. - Deze server wijzigt nooit de facturering.
get_accountleest alleen het abonnement, het gebruik en de status van het abonnement. - Sending requires an active subscription. There is no free allowance. Every send, including a test and a send to the account owner's own address, returns
subscription_required(402) until a plan is active. Lapsed, cancelled, and past-due subscriptions are refused the same way. The owner chooses a plan in the dashboard (Profile & Billing) or at https://sendhq.cc/pricing. Unpaid workspaces can still verify domains, create keys, and read the workspace. - Accepted is not delivered. A successful send returns an ID; delivery, bounce, and complaint evidence arrives later in
list_email_events. Never claim inbox placement or that a person read a message. Broadcast opens are estimates: privacy proxies and security scanners load images on their own, and requests that look automated are counted apart (machineinget_broadcast_report). - Stap niet over op een ander From-adres om een
423-pauze te omzeilen, en voeg afgemelde ontvangers of ontvangers met een klacht nooit opnieuw toe.
API-sleutels vallen buiten de scope
Er zijn bewust geen tools die API-sleutels aanmaken, wijzigen, roteren, intrekken of verwijderen. Een agent mag geen credentials aanmaken of vernietigen. list_api_keys geeft alleen namen, niet-geheime prefixen en het tijdstip van laatste gebruik terug. Sleutelbeheer blijft in het dashboard, bij een ingelogde mens.
Workflows
1. Eerste verzending
get_service_healthbevestigt dat de API bereikbaar is (werkt zonder sleutel).get_accountshows the plan (access.tier) and remaining quota. If there is no active plan, do not send: the call returnssubscription_required.list_sending_identitiestoont de From-adressen die je kunt gebruiken. Is de lijst leeg, doorloop dan eerst de domeinworkflow.- Bevestig afzender, ontvanger, onderwerp en berichttekst met de gebruiker en roep daarna
send_emailaan met eenidempotency_key. list_email_eventsmet het teruggegevenidtoontdelivery,bounce,complaintofrejectzodra de provider dat meldt (meestal binnen seconden tot minuten).
{
"name": "send_email",
"arguments": {
"from": "Acme <hello@example.com>",
"to": [
"owner@example.com"
],
"subject": "SendHQ is connected",
"text": "It works.",
"idempotency_key": "first-send-2026-09-26"
}
}2. Domeinverificatie van begin tot eind
add_domainwithname: "example.com". The result includes the DNS records (DKIM CNAMEs, domain verification, SPF, recommended DMARC).get_dns_providermet dedomain_iddetecteert de gezaghebbende DNS-provider en geeft per record de exacte relatieve host terug die je bij die provider moet invullen.- If
providers.domainConnect.availableis true,get_domain_connect_linkreturns a consent URL. Give it to the human; nothing changes until they approve at the provider. Otherwise, give the human the records to publish. Never publish a second SPF record: merge SendHQ's SPF include (include:amazonses.com) into the existingv=spf1value. verify_domainrechecks DNS and DKIM verification. Status moves throughpending,checking, andpropagatingtoverified. Pollverify_domainorget_domainevery 30–60 seconds; DNS can take minutes to hours.- Als
statusverifiedis, verschijnen de adressen van het domein inlist_sending_identities.
3. Bounces, klachten en suppressies
list_blocked_recipientsgeeft elk geblokkeerd adres terug met de reden (bounce,complaint,unsubscribe) en een totaaloverzicht.list_suppressionsgeeft suppressies door hard bounces en klachten terug;deliverability_statsgeeft bezorg-, bounce- en klachtpercentages over 30 dagen;list_sender_reputationlaat zien welke From-adressen worden afgeremd of gepauzeerd.- Een verzending met een ontvanger op de suppressielijst mislukt met
422 recipient_suppressed. Verwijder die ontvanger en verstuur opnieuw. - Roep
remove_suppressionalleen aan als een mens bevestigt dat een mailbox met een bounce nu weer werkt. Suppressies door klachten zijn permanent (409 complaint_suppression_locked).
4. Inkomende e-mail ontvangen
- Het domein (vaak een subdomein zoals
inbound.example.com) moet geverifieerd zijn. setup_inboundricht ontvangst in en geeft één MX-record terug. Een mens publiceert het.verify_inboundtotdatstatusreadyis.create_inboxmetdomain_idenlocal_part(bijvoorbeeldsupport) maaktsupport@inbound.example.comaan.- Poll
list_emailsmetdirection: "in"enunread: true(optioneelinbox_id). Lees een bericht metget_email, de conversatie metget_thread, bijlagen metdownload_attachment, en markeer het als afgehandeld metmark_email(read: true). - Antwoord in de thread met
send_emailenreply_to_email_id; SendHQ stelt In-Reply-To, References en de thread in.
5. Webhooks en eventnotificaties
Webhooks push signed events to an endpoint a human configures in the dashboard or with the REST API (see /docs/webhooks): email events (email.sent, email.delivered, email.delivery_delayed, email.bounced, email.complained, email.failed, email.received), contact.unsubscribed when a recipient unsubscribes from a marketing or automation email, and, for automations, automation.entered, automation.converted, and automation.exited. There is no webhook tool, because endpoint responses carry signing secrets. An agent without a webhook polls instead: list_email_events for one message's outcome, list_emails with status (for example bounced) or after for recent changes, list_emails with direction: "in" and unread: true for new inbound mail, and list_blocked_recipients for new suppressions. Poll no more than about once a minute per question.
6. Een mislukte bezorging diagnosticeren
- Zoek het bericht:
list_emailsmetdirection: "out"entoofquery, ofget_emailals je het ID hebt.status: failedbetekent dat SendHQ of de provider het bij het aanbieden heeft geweigerd; de fout bij de e-mail legt uit waarom. list_email_events:bounce(permanent of tijdelijk, met de diagnose van de provider),complaint,rejectofdelivery. Nog geen events betekent dat de provider nog niets heeft gemeld; wacht en kijk later opnieuw.- If the send call itself failed, read the error
code:subscription_required→ the owner activates a plan;sender_domain_unverified→ finish domain verification;recipient_suppressed→ the address hard-bounced or complained before;sender_paused→ inspectlist_sender_reputation;account_paused→ the workspace is paused for review, read the rates;daily_limit_reached→ wait until midnight UTC;quota_exhausted→get_accountusage. get_domaincontroleert of DKIM, SPF en DMARC nog gepubliceerd zijn;deliverability_statslaat zien of het probleem één bericht betreft of een trend is.- Rapporteer wat het bewijs laat zien. Een
delivery-event betekent dat de server van de ontvanger het bericht heeft geaccepteerd, niet dat het in de inbox is beland of is gelezen.
7. Een eigen taakbucket (labels)
create_labelmetname(bijvoorbeeldAgent/Orders) enskip_inbox: true. Daarmee wordt het label een bucket: ontvangen e-mail die het label krijgt, wordt gearchiveerd, zodat hij alleen in het label verschijnt en nooit in de Inbox van de mens.- Verstuur taakmail met
send_email(ofsend_batch) enlabels: ["Agent/Orders"]. Antwoorden in die conversatie krijgen automatisch het label en slaan de Inbox over. - Voeg voor e-mail die buiten je conversaties begint een sorteerregel toe:
create_label_rulemetinbox_id(een apart adres zoalsorders@…),from,toofsubject. Geefapply_to_existing: truemee om al ontvangen e-mail ook te sorteren. - Werk de bucket af:
list_emailsmetlabel: "Agent/Orders",direction: "in"enunread: true; lees metget_emailofget_thread, antwoord metsend_emailenreply_to_email_id, en roepmark_emailread: trueaan als het is afgehandeld. - Verplaats een verdwaald bericht naar de bucket of eruit met
label_email(add/remove). Een bucketlabel toevoegen aan een ontvangen bericht archiveert het ook. - Optioneel stuurt
set_inbox_forwardingeen kopie van alles wat een ontvangend adres binnenkrijgt naar een andere mailbox (het doeladres bevestigt eerst per e-mail).
{
"name": "send_email",
"arguments": {
"from": "Orders <orders@example.com>",
"to": [
"customer@example.net"
],
"subject": "Order 1042: confirm delivery window",
"text": "Reply with a time that works.",
"labels": [
"Agent/Orders"
],
"idempotency_key": "order-1042-window"
}
}8. Bijlagen en templates
Voeg op een betaald abonnement maximaal 10 bestanden toe met send_email attachments (elk bestand heeft content_base64 of een lokaal file_path nodig; filename is standaard de basisnaam van het bestand). Voor gehoste templates: create_template → update_template_draft → render_template voor een voorbeeld met voorbeelddata → send_template_test (verstuurt één echte test) → publish_template, en verstuur daarna met send_email of send_batch via template: {key, data} en precies één to-ontvanger.
9. Send a newsletter
- Audience:
list_lists(orcreate_listwith a signup form), and optionallypreview_segmentthencreate_segmentto narrow it, for example to contacts taggedVIPwho opened in the last 90 days. Add only people who asked for your email: every subscribed contact needs aconsent_basis. get_newsletter_settings: ifpostalAddressis empty, ask the user for one and set it withupdate_newsletter_settings(marketing email needs it).create_broadcastwithlist_id, a verifiedfrom,subject,preview_text, content (markdownis simplest), and optionallyaudience(segment_id,limit,order: engaged).check_broadcast: fix everyblockitem and tell the user aboutwarnitems. Thensend_broadcast_testto the user's own address so they can look at it.- Only when the user says to send:
send_broadcastnow (with anidempotency_key), orschedule_broadcastwithscheduled_at(unschedule_broadcastto change it). - Follow up with
get_broadcast(delivery totals),get_broadcast_report(opens, clicks, links, inbox providers, against your average), andlist_broadcast_recipientswithactivity. Report opens as estimates. With a limited audience,send_broadcast_to_moresends to the next people.
{
"name": "create_broadcast",
"arguments": {
"list_id": "lst_…",
"from": "Acme <news@example.com>",
"subject": "What shipped in October",
"preview_text": "Three new features",
"markdown": "Hi {{first_name | there}},\n\nHere is what shipped this month.",
"audience": {
"segment_id": "seg_…"
}
}
}10. Run an automation
An automation is a timed sequence of emails that starts when a contact does something and stops when they convert. Automations are being enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled from every tool below.
create_automationwith akey, theentryevent,exit_rules(thegoal_eventthat counts as converting, orno_goal: true), a verifiedfrom_address, andsteps, each dueoffset_secondsafter the person entered. It starts as a draft and sends nothing. Every automation carriesdomain, the domain of itsfrom_address; in a workspace that sends from several domains,list_automationsandget_automations_overviewtakedomainto show the automations of one of them.- To let the user read it first:
send_automation_test_emailsends one email, andsend_automation_testevery email in order, to the account's own address only (never to a contact), with stand-in values for the merge tags. A test enrols nobody, is in no report, and works while the automation is still a draft. Both send real email, so only when the user asks.send_automation_test_emailwithdry_run: truereturns the rendered email without sending anything. get_sending_limitsshows how much automation email one person may get across every automation, and during which hours. Change them withupdate_sending_limitsonly when the user asks.- To start from a ready-made email instead of writing one:
list_automation_templatesis the template library (welcome, onboarding tips, a nudge to finish setup, trial ending and trial ended, abandoned checkout, failed payment or dunning, receipt, upgrade at a usage limit, feature announcement, review request, feedback score, cancellation survey, and winback for retention),get_automation_templateshows one with the email as this workspace would send it, anduse_automation_templatemakes the draft automation with the emails, the suggested entry event and the suggested goal. Some templates come as a set that makes one automation: three onboarding tips, trial ending then trial ended, payment failed then a last notice.set_automation_stepwithtemplateloads one template into an email of an automation that already exists. - An email can also be built in the dashboard's drag-and-drop builder.
get_automationshows such an email witheditordesign: itscontentis the builder's project, which only the builder writes, and itshtmlis what is sent. Leave the project alone. To change the wording of a designed email, ask the user to open it in the dashboard; to replace it, send your ownhtmlwitheditorhtml. - A template is finished except for what only the user knows, written as placeholders in square brackets:
[First step], or[Link to plans]as a link's address.to_fillon the automation lists each one by email, and each workspace name the emails print that is blank. Ask the user for the real words and links, write them in withset_automation_step, and setproduct_nameandsender_namewithupdate_sending_limits. Never invent them.set_automation_statusrefuses to turn the automation on while anything is left (422automation_not_ready, with aproblemslist that names each email and detail); test emails are allowed, so the user can read it first. - Only when the user says to start:
set_automation_statuswithstatus: "on". - Record what people do with
track_event(a new contact needscontact.consent_basis). The entry event starts the sequence, the goal event ends it as converted, and adedupe_keymakes a retry harmless.enroll_contactandexit_contactadd or remove one person by hand. preview_automationshows, for everyone in the automation now, which email would go out if they were evaluated at this moment, or why not: nothing due until a time, held by a limit or the sending hours until a time, waiting behind a higher-priority automation, or skipped. It sends nothing and changes nothing.list_automationsgives each automation's 30-day totals. An email that a limit holds back is not dropped: it goes out when the limit allows. When several emails of one automation are due at once, only the latest is sent.- Results:
get_automations_overview(every automation) andget_automation_report(one automation, with a row per email) give totals and a number for each day of a date range: people who entered, emails sent, delivered, opened, clicked, and converted.list_automation_peoplelists who did what (did: entered, sent, delivered, opened, clicked, converted, bounced, unsubscribed, or waiting), andget_automation_persongives one contact's history with every open and click. Automation emails are tracked like broadcasts: report opens and clicks as estimates, and note that automated requests are labelledmachineand never counted.
{
"name": "use_automation_template",
"arguments": {
"template_id": "payment-failed-notices",
"from_name": "Dana from Acme",
"from_address": "dana@example.com"
}
}{
"name": "preview_automation",
"arguments": {
"automation_key": "checkout-recovery"
}
}{
"name": "list_automation_people",
"arguments": {
"automation_key": "checkout-recovery",
"did": "clicked",
"step": 1
}
}11. See what came in, and connect another system
Events reach SendHQ three ways: track_event from the workspace's own code, a connection (a secret address a payment provider or another system posts its webhooks to), and a spreadsheet uploaded in the dashboard. See /docs/events.
list_eventsis the feed of everything recorded, newest first: who, what they did (also as plain words), when, where it came from, and which automations it started, ended, or converted. Filter bycontact, byname, or by date.list_event_nameslists the kinds of event seen in the last 30 days.list_connectionsshows each connection with its last delivery in plain words, andget_connectionits last 50 deliveries: "Recorded 2 events", "Skipped: no email address", "Refused: bad signature". Start there when something a provider sent did not show up.- Only when the user asks to connect a system:
create_connectionwithkindstripeordodo(mapped for you) orgenericwith amapping. It returns the secretaddressonce; give it to the user to paste into that system. From then on what arrives is recorded without anyone looking, and can start automations that send email. update_connectionwithenabled: falsepauses a connection (its address answers 404);delete_connectionremoves it. The provider's signing secret and a replacement address are set by a person in the dashboard.
{
"name": "list_events",
"arguments": {
"contact": "ada@example.net"
}
}12. Check an email's content before it is sent
score_email reads a subject, the HTML and the plain text as they were written and returns a score from 0 to 100 with what to change, most points first. A plain email with no links and no images scores 100; a designed layout, links to another site than the sender's, link shorteners, images with few words, hidden text, capitals and very long HTML each take points off. Pass from so links can be compared with the sender's own domain. Nothing is stored or sent, and the footer and tracking SendHQ adds are not scored. The dashboard's email editor shows the same number for the same content. It looks at content only, so use it as a checklist: sender reputation, authentication and how recipients react decide more of where mail lands.
{
"name": "score_email",
"arguments": {
"from": "hello@example.com",
"subject": "Your cart is still here",
"html": "<p>Pick up where you left off.</p><p><a href=\"https://bit.ly/3xyz\">Finish checkout</a></p>"
}
}Resultaten, paginering en fouten
Een geslaagde call geeft het JSON-object van de API terug als structuredContent en als JSON-tekstblok. Elke list_*-tool accepteert limit (1–200, standaard 50) en offset, en voegt een pagination-object toe. Blijf aanroepen met offset: pagination.next_offset zolang has_more true is.
{
"data": [
"…"
],
"count": 50,
"pagination": {
"offset": 0,
"limit": 50,
"returned": 50,
"total": 180,
"has_more": true,
"next_offset": 50
}
}Een mislukte call geeft isError: true terug met een gestructureerde fout. Volg remedy in plaats van blind opnieuw te proberen; probeer alleen opnieuw als retryable true is.
{
"error": {
"code": "subscription_required",
"status": 402,
"message": "Sending requires an active SendHQ subscription. Choose a plan to start sending.",
"retryable": false,
"explanation": "This workspace has no active paid subscription. SendHQ does not send any email, including to the account owner, until a plan is active.",
"remedy": "Ask the account owner to choose a plan at https://sendhq.cc/pricing or in the dashboard (Profile & Billing). Do not retry until the subscription is active."
}
}Optionele foutvelden: request_id (vermeld die bij support), retry_after_seconds, problems (lijst met schemaschendingen bij invalid_arguments) en idempotent_replayed (zie Idempotentie).
Idempotentie
send_email en send_batch accepteren idempotency_key (maximaal 200 tekens), die wordt meegestuurd als Idempotency-Key-header. Genereer één stabiele sleutel per logisch bericht, bijvoorbeeld invoice-4812-receipt.
- Een retry moet dezelfde sleutel EN een identieke requestbody gebruiken. Dezelfde sleutel met welke wijziging dan ook (ontvanger, onderwerp, berichttekst, header, templatedata, zelfs argumentwaarden) geeft
409 idempotency_conflict. - Dezelfde sleutel, dezelfde body, origineel afgerond: SendHQ geeft het opgeslagen resultaat terug zonder opnieuw te versturen. Zo probeer je het veilig opnieuw na een time-out of
network_error. - Dezelfde sleutel terwijl het origineel nog loopt:
409 idempotency_in_progress, na korte tijd opnieuw te proberen. - Een nieuw logisch bericht heeft een nieuwe sleutel nodig.
- Opgeslagen fouten worden ook opnieuw afgespeeld. Is de eerste poging mislukt, dan geeft een retry met dezelfde sleutel diezelfde fout terug met
idempotent_replayed: trueenretryable: false. Controleer metlist_emails(direction: out) dat er niets is verstuurd, los de oorzaak op en verstuur daarna met een nieuwe sleutel. - De server probeert een POST nooit uit zichzelf opnieuw. Alleen alleen-lezen GET-calls worden automatisch opnieuw geprobeerd (maximaal 3 pogingen bij netwerkfouten, 429 en 5xx).
send_emailmet inlineattachmentskan geenidempotency_keymeekrijgen, omdat het meerdere requests uitvoert. Voor verzendingen met bijlagen die veilig opnieuw kunnen:create_draft→upload_attachment→send_emailmetdraft_idenidempotency_key.
{
"name": "send_email",
"arguments": {
"from": "Acme <billing@example.com>",
"to": [
"owner@example.com"
],
"subject": "Receipt #4812",
"text": "Thanks for your payment.",
"idempotency_key": "receipt-4812"
}
}Rate limits en quota
SendHQ publiceert geen vaste limiet voor het aantal requests per seconde op de API. De limieten waar een agent echt tegenaan loopt, zijn gebruikslimieten, die als 429 worden teruggegeven:
- Maandelijkse afleveringen aan ontvangers per abonnement. Elk To-, Cc- en Bcc-adres telt als één aflevering. Zie
get_account→usage.recipientDeliveriesvs.usage.emailQuotaMonth. - Dagelijkse ontvangers per exact From-adres, bepaald door de reputatiestatus van die afzender (
list_sender_reputation→dailyLimit, standaard 2.000 op betaalde abonnementen). - Subscription: sending is refused with
subscription_requireduntil a paid plan is active. There is no free or trial allowance. - Workspace daily ladder on paid plans: 1,000 recipients on day one, then 2,000, 3,000, 5,000, 8,000, 12,000, 18,000, 25,000, 35,000, 45,000, and 50,000. A step is gained after a UTC day that used at least half the cap with healthy 7-day feedback. A high rate demotes once per incident, not every day the rate stays high. See
get_account→sendingLimit. Over the cap:daily_limit_reached, not queued, retry afterresets_at(midnight UTC), not on a short backoff. - Hourly pace: about one tenth of the day's cap each UTC hour (100 on day one).
hourly_limit_reachedwaits until the next UTC hour. - New domains: a sending domain less than 30 days old may send at most 500 Gmail recipients a day (
gmail_recipient_limit), on any ladder rung.gmail_rate_limitedmeans Gmail returned 4.7.28; wait untilresets_atand keep sending to other providers. - Bijlagen: maximaal 10 bestanden en 10 MB per bericht; 10 GB aan bijlagenverkeer per maand, gewogen naar ontvangers, op betaalde abonnementen.
- Per request: To + Cc + Bcc tot 100 adressen;
send_batchtot 100 berichten. - Reputatie-circuitbreaker: in een rollend venster van 7 dagen zorgen bounces of klachten boven de drempel ervoor dat één From-adres wordt afgeremd of gepauzeerd (
423 sender_paused). Het herstelt automatisch zodra de percentages dalen.
quota_exhausted kun je pas opnieuw proberen als de periode opnieuw begint of het abonnement verandert. rate_limited kun je opnieuw proberen na retry_after_seconds; probeer verzendingen opnieuw met dezelfde idempotency_key en een identieke body.
Foutencatalogus
code is stabiel; baseer je logica daarop en niet op message.
| code | HTTP | Opnieuw? | Wat het betekent en wat je moet doen |
|---|---|---|---|
invalid_arguments | — | nee | De argumenten voldeden lokaal niet aan het JSON Schema van de tool; er is niets bij SendHQ aangekomen. Corrigeer de velden die in problems staan. |
auth_error | 401 | nee | Ontbrekende, ingetrokken of verkeerde API-sleutel. Stel SENDHQ_API_KEY in voor het serverproces; een mens maakt sleutels aan in het dashboard. |
subscription_required | 402 | nee | No active subscription. Nothing is sent, including to the account owner. The owner chooses a plan. Do not retry until then. |
payment_required | 402 | nee | De functie vereist een betaald abonnement (bijvoorbeeld bijlagen). Verstuur zonder, of upgrade. |
sender_domain_not_owned | 403 | nee | Het From-domein hoort niet bij deze workspace. Gebruik list_sending_identities of add_domain. |
sender_domain_unverified | 403 | nee | Het From-domein is nog niet geverifieerd. get_domain, ontbrekende records publiceren, verify_domain. |
domain_limit_reached | 403 | nee | De domeinlimiet van het abonnement is bereikt. Verwijder een ongebruikt domein (na goedkeuring) of upgrade. |
marketing_not_enabled | 403 | nee | De marketingklasse is niet ingeschakeld voor dit domein of abonnement. Gebruik transactional alleen als het bericht echt transactioneel is. |
forbidden | 403 | nee | Het beleid staat de bewerking niet toe. Pas het request aan. |
not_found | 404 | nee | Het ID hoort niet bij deze workspace. Vraag de resource op om het juiste ID te vinden; herstel gearchiveerde templates eerst. |
idempotency_conflict | 409 | nee | Sleutel hergebruikt met een andere body. Verstuur exact het origineel opnieuw, of gebruik een nieuwe sleutel voor een nieuw bericht. |
idempotency_in_progress | 409 | ja | Het oorspronkelijke request loopt nog. Wacht en probeer het dan opnieuw met dezelfde sleutel en body. |
revision_conflict | 409 | nee | Het templateconcept is gewijzigd sinds je het las. get_template, samenvoegen, opnieuw opslaan. |
complaint_suppression_locked | 409 | nee | De ontvanger heeft een klacht ingediend. Stuur hem nooit meer e-mail. |
inbound_not_ready | 409 | nee | Ontvangst van inkomende e-mail is nog niet klaar. setup_inbound, MX publiceren, verify_inbound. |
conflict | 409 | nee | De resource bestaat al of heeft de verkeerde status. Lees hem en pas aan. |
attachments_too_large | 413 | nee | Meer dan 10 bestanden of 10 MB. Verwijder bijlagen of maak ze kleiner. |
recipient_suppressed | 422 | nee | Een ontvanger gaf eerder een hard bounce of een klacht. Verwijder die; zie list_blocked_recipients. |
recipient_unsubscribed | 422 | nee | Een ontvanger heeft zich afgemeld voor marketingmail. Verwijder die permanent. |
validation_failed | 422 | nee | Inhoud geweigerd, bijvoorbeeld templatedata die het variabelencontract schendt. Corrigeer de invoer. |
sender_paused | 423 | nee | Dit From-adres is gepauzeerd door de circuitbreaker voor bounces/klachten over 7 dagen. Stop, herstel de lijst en wacht op automatisch herstel. |
account_paused | 423 | nee | Workspace paused for a deliverability review. The body has the measured rate and the limit when the pause was for bounces or complaints. Do not send until it is restored. |
quota_exhausted | 429 | nee | Monthly allowance, per-sender daily limit, or attachment transfer. Not the workspace daily ladder. Check get_account; wait for that limit to reset or upgrade. |
daily_limit_reached | 429 | after reset | Workspace daily ladder. Not a short backoff. Wait until resets_at (midnight UTC). The message was not queued. |
hourly_limit_reached | 429 | after reset | Hourly pace (about a tenth of the day's cap). Wait until the next UTC hour. Not a short backoff. |
gmail_recipient_limit | 429 | after reset | 500 Gmail recipients a day for a sending domain under 30 days old, on any ladder rung. Wait until midnight UTC. Not queued. |
gmail_rate_limited | 429 | after reset | Gmail returned 4.7.28 for this domain. Wait until resets_at. Other providers keep sending. |
rate_limited | 429 | ja | Slow down; wait retry_after_seconds. This is not a daily, hourly, or Gmail cap. |
server_error | 5xx | ja | Tijdelijke fout bij SendHQ of de provider. Wacht met backoff en probeer opnieuw; verzendingen met dezelfde sleutel en body. Is idempotent_replayed true, gebruik dan een nieuwe sleutel nadat je hebt bevestigd dat er niets is verstuurd. |
network_error | — | ja | Request of respons verloren gegaan. Probeer opnieuw; bij verzendingen maakt dezelfde idempotency_key dat veilig. |
invalid_request | 400 | nee | Ongeldig request. Lees message en corrigeer het. |
tool_error | — | nee | Lokale fout binnen de MCP-server (bijvoorbeeld een onleesbaar file_path). Lees message. |
Toolreferentie
Elke tool met zijn veiligheidsklasse, het REST-endpoint dat hij aanroept, zijn parameters, de responsstructuur en een voorbeeld van een params-object voor tools/call. De parameters zijn exact: de server weigert alles wat niet vermeld staat.
Emails and threads: send_email, send_batch, list_emails, get_email, mark_email, delete_email, list_email_events, get_thread, email_delivery, thread_delivery
Labels and auto-filing rules: list_labels, get_label, create_label, update_label, delete_label, create_label_rule, delete_label_rule, label_email
Drafts, attachments, and sender identities: list_sending_identities, create_draft, list_drafts, get_draft, update_draft, delete_draft, upload_attachment, download_attachment, delete_attachment
Hosted templates: list_templates, create_template, get_template, update_template_draft, create_template_draft, render_template, send_template_test, publish_template, archive_template, restore_template
Domains and DNS: list_domains, get_domain, add_domain, verify_domain, delete_domain, get_dns_provider, get_domain_connect_link
Inbound email: setup_inbound, verify_inbound, list_inboxes, get_inbox, create_inbox, update_inbox, set_inbox_forwarding, delete_inbox
Deliverability, bounces, and suppressions: deliverability_stats, deliverability_account, deliverability_domains, deliverability_senders, score_email, list_sender_reputation, list_suppressions, remove_suppression, list_blocked_recipients
Campaigns: list_contacts, create_contact, upsert_contact, get_contact, update_contact, delete_contact, import_contacts, list_contact_imports, bulk_update_contacts, list_tags, list_contact_fields, set_contact_field, delete_contact_field, list_segments, get_segment, preview_segment, create_segment, update_segment, delete_segment, list_lists, create_list, get_list, update_list, delete_list, add_list_contacts, remove_list_contact, list_broadcasts, create_broadcast, get_broadcast, update_broadcast, delete_broadcast, send_broadcast, cancel_broadcast, list_broadcast_recipients, check_broadcast, send_broadcast_test, schedule_broadcast, unschedule_broadcast, duplicate_broadcast, send_broadcast_to_more, get_broadcast_report, get_newsletter_settings, update_newsletter_settings, get_campaign_overview, list_uploaded_images
Automations, events, and sending limits: track_event, list_automations, get_automation, create_automation, update_automation, delete_automation, set_automation_step, delete_automation_step, set_automation_step_variant, set_automation_status, send_automation_test_email, send_automation_test, enroll_contact, exit_contact, preview_automation, get_automations_overview, get_automation_report, list_automation_people, get_automation_person, get_sending_limits, update_sending_limits, list_automation_templates, get_automation_template, use_automation_template, list_events, list_event_names, list_connections, get_connection, create_connection, update_connection, delete_connection
Account, usage, analytics, and keys: get_account, get_account_diagnostics, get_analytics, list_api_keys, get_service_health
Geen tools gevonden voor dit filter.
E-mails en threads
send_emailEén e-mail verzenden
SENDS REAL EMAIL. Send one message from a verified domain: raw html/text, a published hosted template, a reply in an existing thread, or a message with attachments. Pass idempotency_key so a retry cannot send twice; a retry must reuse the same key AND an identical request, otherwise SendHQ returns 409. attachments is a convenience that creates a draft, uploads each file, and sends with that draft; it cannot be combined with idempotency_key or draft_id (use create_draft + upload_attachment + send_email with draft_id for retry-safe attachment sends). Unpaid workspaces (integration trial) can deliver only to the account email or a mailbox-simulator test address, and cannot send attachments.
Geef minstens één van deze op: html, text, template.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
from | string | ja | Afzender, bijv. Acme <hello@example.com>. Het domein moet in deze workspace geverifieerd zijn (zie list_sending_identities). (max. 998 tekens) |
to | string[] | ja | Ontvangers. Elk item is een adres, optioneel met een weergavenaam. To+cc+bcc mogen samen maximaal 100 zijn; elke bestemming verbruikt één bezorgcredit. (1–100 items) |
cc | string[] | nee | Ontvangers in cc. (0–100 items) |
bcc | string[] | nee | Ontvangers in bcc. (0–100 items) |
subject | string | nee | Onderwerpregel. Laat weg bij het versturen van een template. (max. 998 tekens) |
text | string | nee | Berichttekst in plaintext. Geef text, html of template op. |
html | string | nee | HTML-berichttekst. SendHQ saneert die en leidt de tekst af als text ontbreekt. |
reply_to | string | nee | Reply-To-adres. |
headers | object | nee | Extra veilige custom headers (stringwaarden), bijv. {"X-Entity-Ref-ID": "123"}. Routeringsheaders zoals From/To/Message-ID worden door SendHQ beheerd. |
message_class | string | nee | transactional (standaard) of marketing. Marketing vereist een abonnement of domein waarop marketing is ingeschakeld en voegt afmeldafhandeling toe. (een van transactional, marketing) |
reply_to_email_id | string | nee | Antwoord binnen een bestaande conversatie: het em_…-ID van het bericht waarop je antwoordt. SendHQ stelt In-Reply-To/References en de thread in. |
thread_id | string | nee | Expliciet thread-ID waaronder het bericht wordt opgeslagen. |
draft_id | string | nee | Verstuur de bijlagen van een opgeslagen concept met dit bericht (dr_…). Het concept wordt na een geslaagde verzending verwijderd. |
template | object | nee | Verstuur een gepubliceerde gehoste template in plaats van ruwe html/tekst. Vereist precies één to-ontvanger en geen cc/bcc; de template levert het onderwerp. Geef minstens één van deze op: id, key. |
template.id | string | nee | Template-ID (tmpl_…). Geef id of key op. |
template.key | string | nee | Templatekey, zoals account-welcome. Geef id of key op. |
template.version_id | string | nee | Optioneel ID van een gepubliceerde release (tmplv_…). Standaard de huidige gepubliceerde release. |
template.data | object | nee | Waarden voor de getypeerde variabelen van de template. |
labels | string[] | nee | Labelnamen of lbl_…-ID's waaronder dit bericht wordt opgeslagen. Onbekende namen worden aangemaakt. Antwoorden in de conversatie krijgen dezelfde labels, en een bucketlabel (skip_inbox) houdt die antwoorden uit de Inbox. Max. 10. (0–10 items) |
idempotency_key | string | nee | Idempotency-Key-header (max. 200 tekens). Hergebruik die alleen om exact dit request opnieuw te proberen. (max. 200 tekens) |
attachments | object[] | nee | Bij te voegen bestanden (max. 10 bestanden, 10 MB in totaal). Elk bestand heeft content_base64 (plus filename) of een lokaal file_path nodig. (0–10 items) Geef minstens één van deze op: content_base64, file_path. |
attachments[].filename | string | nee | Bestandsnaam die de ontvanger ziet. Verplicht bij content_base64; standaard de basisnaam van file_path. (max. 255 tekens) |
attachments[].content_type | string | nee | MIME-type, bijv. application/pdf. Standaard application/octet-stream. |
attachments[].content_base64 | string | nee | Standaard base64-inhoud van het bestand. |
attachments[].file_path | string | nee | Absoluut pad van een lokaal bestand dat het MCP-serverproces kan lezen. |
{
"name": "send_email",
"arguments": {
"from": "Acme <hello@example.com>",
"to": [
"owner@example.com"
],
"subject": "Your export is ready",
"text": "Download it from your dashboard.",
"idempotency_key": "export-ready-42"
}
}send_batchEen batch individuele e-mails verzenden
SENDS REAL EMAIL. Verstuurt 1–100 onafhankelijke berichten in één request (gebruik dit voor templatepersonalisatie per ontvanger). Elk item heeft dezelfde structuur als send_email (zonder attachments/idempotency_key). Items slagen of mislukken afzonderlijk: HTTP 207 betekent gedeeltelijk succes; controleer elke data[i].ok en data[i].error. Eén idempotency_key geldt voor de hele batchbody.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
emails | object[] | ja | Te verzenden berichten. (1–100 items) Geef minstens één van deze op: html, text, template. |
idempotency_key | string | nee | Idempotency-Key voor de hele batch (max. 200 tekens). (max. 200 tekens) |
{
"name": "send_batch",
"arguments": {
"emails": [
{
"from": "Acme <hello@example.com>",
"to": [
"owner@example.com"
],
"template": {
"key": "account-welcome",
"data": {
"first_name": "Asha"
}
}
}
],
"idempotency_key": "welcome-batch-2026-09-26"
}
}list_emailsE-mail opvragen en doorzoeken
Vraagt verzonden (direction: out) en ontvangen (direction: in) e-mail op, nieuwste eerst, met filters. Ontvangen e-mail wordt geclassificeerd: lees de inbox van de mens met direction: in, archived: false, category: primary; triage met important: true; spam is verborgen, tenzij category: spam of include_spam: true. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
direction | string | nee | in voor ontvangen, out voor verzonden. (een van in, out) |
status | string | nee | Statusfilter, bijv. queued, sent, delivered, bounced, complained, failed. |
domain | string | nee | Alleen berichten voor dit domein, of een kommagescheiden lijst met domeinen (matcht op elk ervan). |
inbox_id | string | nee | Alleen berichten die door deze inbox zijn ontvangen (inb_…). |
label | string | nee | Alleen berichten met dit label: een label-ID lbl_… of de exacte naam, of een kommagescheiden lijst (matcht op elk ervan). Gebruik list_labels om de mappen te zien. |
archived | boolean | nee | false = de Inbox-weergave (ontvangen e-mail die niet is gearchiveerd), true = alleen gearchiveerd. Laat weg voor alle e-mail. |
category | string | nee | primary (mensen), updates (nieuwsbrieven, bulk, geautomatiseerd) of spam; of een kommagescheiden lijst. Spam is verborgen, tenzij je erom vraagt. |
important | boolean | nee | true = alleen berichten die als belangrijk zijn gemarkeerd (antwoorden op conversaties die jij bent begonnen en afzenders die als belangrijk zijn gemarkeerd). |
include_spam | boolean | nee | Neem spam op in de resultaten (voor zoekopdrachten in alle mappen). |
from | string | nee | Afzenderadres bevat deze waarde. |
to | string | nee | Ontvangersadres bevat deze waarde. |
unread | boolean | nee | true = alleen ongelezen, false = alleen gelezen. |
after | string | nee | ISO-8601-tijdstempel; alleen berichten die daarna zijn aangemaakt. (date-time) |
before | string | nee | ISO-8601-tijdstempel; alleen berichten die daarvoor zijn aangemaakt. (date-time) |
query | string | nee | Vrije-tekstzoekopdracht in onderwerpen, berichtteksten, adressen van afzenders/ontvangers en bestandsnamen van bijlagen. (max. 200 tekens) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_emails",
"arguments": {
"direction": "in",
"unread": true,
"limit": 25
}
}get_emailEén e-mail ophalen
Haalt één bericht op met headers, html-/tekstbody, status, threadmetadata en metadata van bijlagen (download de bytes met download_attachment).
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email_id | string | ja | E-mail-ID (begint met em_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "get_email",
"arguments": {
"email_id": "em_123"
}
}mark_emailMarkeren als gelezen, gearchiveerd, spam of belangrijk
Werkt één bericht bij: read, archived, category (primary, updates, spam; alleen ontvangen e-mail) en important. Als je spam meldt of iets als belangrijk markeert, leert SendHQ dat over die afzender voor toekomstige e-mail; geef learn: false mee om alleen dit bericht te wijzigen. Geef minstens één veld op.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email_id | string | ja | E-mail-ID (begint met em_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
read | boolean | nee | true = gelezen, false = ongelezen. |
archived | boolean | nee | true = archiveren (de Inbox overslaan), false = terugzetten naar de Inbox. |
category | string | nee | Verplaats een ontvangen bericht naar primary, updates of spam. (een van primary, updates, spam) |
important | boolean | nee | Markeer het bericht als belangrijk of haal die markering weg. |
learn | boolean | nee | false = dit oordeel niet onthouden voor de afzender (standaard true). |
{
"name": "mark_email",
"arguments": {
"email_id": "em_123",
"read": true
}
}delete_emailEen e-mail verwijderen
DESTRUCTIVE: verwijdert een bewaard bericht en de opgeslagen bijlagen permanent uit SendHQ. Een bericht dat al is afgeleverd, wordt niet teruggehaald.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email_id | string | ja | E-mail-ID (begint met em_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "delete_email",
"arguments": {
"email_id": "em_123"
}
}list_email_eventsBezorgevents van een e-mail opvragen
Provider-events voor één verzonden bericht: delivery, bounce, complaint, reject, open, click. Dit is het bewijs of een bericht is afgeleverd of waarom het is mislukt. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email_id | string | ja | E-mail-ID (begint met em_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_email_events",
"arguments": {
"email_id": "em_123"
}
}get_threadEen conversatie ophalen
Haalt alle berichten in een conversatie op in chronologische volgorde (verzonden en ontvangen), elk met metadata van de bijlagen.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
thread_id | string | ja | Thread-ID (meestal het em_…-ID van het eerste bericht; zie threadId bij elke e-mail). (max. 128 tekens) |
{
"name": "get_thread",
"arguments": {
"thread_id": "em_123"
}
}email_deliveryGet an email delivery timeline
Queued, sent, delivered, delayed, bounced, complained, and failed events for one email, with bounce type and the SMTP diagnostic. Reasons are plain text.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email_id | string | ja | |
limit | integer | nee | |
offset | integer | nee |
{
"name": "email_delivery",
"arguments": {
"email_id": "em_123"
}
}thread_deliveryGet a thread delivery summary
Counts of delivered, bounced, complained, and failed outbound messages in one conversation, plus each message's failure reason.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
thread_id | string | ja |
{
"name": "thread_delivery",
"arguments": {
"thread_id": "thr_123"
}
}Labels en automatische sorteerregels
list_labelsLabels opvragen
Vraagt de labels (mappen) van de workspace op met het totale aantal en het aantal ongelezen berichten, plus hun automatische sorteerregels. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_labels",
"arguments": {}
}get_labelEen label ophalen
Haalt één label op met aantallen en automatische sorteerregels.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
label_id | string | ja | Label-ID (begint met lbl_) of de exacte labelnaam. (max. 128 tekens) |
{
"name": "get_label",
"arguments": {
"label_id": "Billing"
}
}create_labelEen label aanmaken
Maakt een label in mapstijl aan. Zet skip_inbox: true om er een bucket van een agent van te maken: verstuur met labels: [name] en de antwoorden worden in het label opgeslagen en uit de Inbox gehouden. Optionele automatische sorteerregels sorteren nieuwe verzonden/ontvangen e-mail (elke voorwaarde van een regel moet overeenkomen). Zet apply_to_existing om ook bewaarde e-mail te sorteren.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | ja | Labelnaam, bijv. Billing of Clients/Acme. Uniek per workspace (hoofdletterongevoelig). (max. 64 tekens) |
color | string | nee | Hexkleur zoals #1a73e8. Optioneel. |
skip_inbox | boolean | nee | Bucketmodus: ontvangen e-mail die dit label krijgt (via een regel, via een antwoord op een conversatie die met dit label is verzonden, of handmatig) wordt gearchiveerd, zodat hij alleen in het label verschijnt en niet in de Inbox. |
rules | object[] | nee | Optionele automatische sorteerregels (max. 20). Elke regel heeft minstens een van inbox_id, from, to, subject nodig. (0–20 items) |
rules[].direction | string | nee | Alleen in (ontvangen) of out (verzonden) e-mail. Laat weg voor beide. (een van in, out) |
rules[].inbox_id | string | nee | Alleen e-mail die door deze inbox is ontvangen (inb_…). Sorteert elk ontvangend adres in een eigen map. |
rules[].from | string | nee | Afzender bevat deze tekst (hoofdletterongevoelig), bijv. @stripe.com. (max. 200 tekens) |
rules[].to | string | nee | To/Cc bevat deze tekst (hoofdletterongevoelig). (max. 200 tekens) |
rules[].subject | string | nee | Onderwerp bevat deze tekst (hoofdletterongevoelig). (max. 200 tekens) |
rules[].skip_inbox | boolean | nee | Archiveer overeenkomende ontvangen e-mail, zodat die alleen in de labelmap verschijnt en niet in de Inbox. |
apply_to_existing | boolean | nee | Sorteer ook al bewaarde e-mail die aan de regels voldoet. |
{
"name": "create_label",
"arguments": {
"name": "Agent/Orders",
"skip_inbox": true,
"rules": [
{
"from": "@stripe.com"
}
]
}
}update_labelEen label hernoemen, van kleur veranderen of er een bucket van maken
Hernoemt een label, wijzigt de kleur of schakelt de bucketmodus (skip_inbox) in of uit. Als je de bucketmodus inschakelt, wordt ontvangen e-mail die al in het label staat gearchiveerd.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
label_id | string | ja | Label-ID (begint met lbl_) of de exacte labelnaam. (max. 128 tekens) |
name | string | nee | Nieuwe naam. (max. 64 tekens) |
color | string | nee | Nieuwe hexkleur. |
skip_inbox | boolean | nee | Bucketmodus: ontvangen e-mail die dit label krijgt (via een regel, via een antwoord op een conversatie die met dit label is verzonden, of handmatig) wordt gearchiveerd, zodat hij alleen in het label verschijnt en niet in de Inbox. |
{
"name": "update_label",
"arguments": {
"label_id": "lbl_123",
"name": "Finance/Billing"
}
}delete_labelEen label verwijderen
DESTRUCTIVE: verwijdert een label en de regels ervan. De e-mail zelf blijft bewaard; die verliest alleen dit label.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
label_id | string | ja | Label-ID (begint met lbl_) of de exacte labelnaam. (max. 128 tekens) |
{
"name": "delete_label",
"arguments": {
"label_id": "lbl_123"
}
}create_label_ruleEen automatische sorteerregel toevoegen
Voegt een regel aan een label toe, zodat overeenkomende nieuwe e-mail automatisch wordt gesorteerd. Elke voorwaarde die je instelt, moet overeenkomen. Gebruik inbox_id om een ontvangend adres een eigen map te geven; voeg skip_inbox toe om die e-mail uit de Inbox te houden.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
label_id | string | ja | Label-ID (begint met lbl_) of de exacte labelnaam. (max. 128 tekens) |
direction | string | nee | Alleen in (ontvangen) of out (verzonden) e-mail. Laat weg voor beide. (een van in, out) |
inbox_id | string | nee | Alleen e-mail die door deze inbox is ontvangen (inb_…). Sorteert elk ontvangend adres in een eigen map. |
from | string | nee | Afzender bevat deze tekst (hoofdletterongevoelig), bijv. @stripe.com. (max. 200 tekens) |
to | string | nee | To/Cc bevat deze tekst (hoofdletterongevoelig). (max. 200 tekens) |
subject | string | nee | Onderwerp bevat deze tekst (hoofdletterongevoelig). (max. 200 tekens) |
skip_inbox | boolean | nee | Archiveer overeenkomende ontvangen e-mail, zodat die alleen in de labelmap verschijnt en niet in de Inbox. |
apply_to_existing | boolean | nee | Sorteer ook al bewaarde e-mail die overeenkomt. |
{
"name": "create_label_rule",
"arguments": {
"label_id": "Billing",
"inbox_id": "inb_123",
"skip_inbox": true
}
}delete_label_ruleEen automatische sorteerregel verwijderen
DESTRUCTIVE: verwijdert één automatische sorteerregel. E-mail die al is gesorteerd, houdt zijn label.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
label_id | string | ja | Label-ID (begint met lbl_) of de exacte labelnaam. (max. 128 tekens) |
rule_id | string | ja | Regel-ID (begint met lrule_), uit get_label. (max. 128 tekens) |
{
"name": "delete_label_rule",
"arguments": {
"label_id": "lbl_123",
"rule_id": "lrule_123"
}
}label_emailLabels aan een e-mail toevoegen of ervan verwijderen
Verplaatst een bericht tussen mappen: voeg labels toe en/of verwijder ze op naam of lbl_…-ID. Onbekende namen in add worden aangemaakt, tenzij create false is.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email_id | string | ja | E-mail-ID (begint met em_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
add | string[] | nee | Toe te voegen labels. (0–10 items) |
remove | string[] | nee | Te verwijderen labels. (0–10 items) |
create | boolean | nee | Maak onbekende labels in add aan (standaard true). |
{
"name": "label_email",
"arguments": {
"email_id": "em_123",
"add": [
"Billing"
],
"remove": [
"Support"
]
}
}Concepten, bijlagen en afzenderidentiteiten
list_sending_identitiesGeverifieerde afzenderidentiteiten opvragen
Adressen en domeinen waarvandaan deze workspace op dit moment kan versturen (geverifieerde domeinen, hun standaard-From en actieve inboxadressen). Roep dit aan vóór send_email om een geldige from te kiezen.
Geen parameters.
{
"name": "list_sending_identities",
"arguments": {}
}create_draftEen concept aanmaken
Maakt een concept in de editor aan. Concepten bevatten bijlagen: maak een concept aan, roep upload_attachment aan en daarna send_email met draft_id. Verstuurt niets.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
from | string | nee | Afzenderadres op een geverifieerd domein (mag leeg zijn tijdens het opstellen). |
to | string[] | nee | Ontvangers. (0–100 items) |
cc | string[] | nee | Ontvangers in cc. (0–100 items) |
bcc | string[] | nee | Ontvangers in bcc. (0–100 items) |
subject | string | nee | Onderwerpregel. (max. 998 tekens) |
html | string | nee | HTML-berichttekst. |
text | string | nee | Berichttekst in plaintext. |
reply_to_email_id | string | nee | E-mail-ID waarop dit concept antwoordt. |
thread_id | string | nee | Thread-ID waar dit concept bij hoort. |
{
"name": "create_draft",
"arguments": {
"from": "hello@example.com",
"to": [
"owner@example.com"
],
"subject": "Invoice"
}
}list_draftsConcepten opvragen
Vraagt concepten uit de editor op, meest recent bijgewerkt eerst. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_drafts",
"arguments": {}
}get_draftEen concept ophalen
Haalt één concept op met de metadata van de bijlagen.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
draft_id | string | ja | Concept-ID (begint met dr_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "get_draft",
"arguments": {
"draft_id": "dr_123"
}
}update_draftInhoud van een concept vervangen
Vervangt de inhoud en ontvangers van een concept. Dit is een volledige vervanging: velden die je weglaat, worden leeggemaakt, dus lees eerst get_draft en stuur elk veld mee dat je wilt behouden. Bijlagen blijven ongewijzigd.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
draft_id | string | ja | Concept-ID (begint met dr_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
from | string | nee | Afzenderadres op een geverifieerd domein (mag leeg zijn tijdens het opstellen). |
to | string[] | nee | Ontvangers. (0–100 items) |
cc | string[] | nee | Ontvangers in cc. (0–100 items) |
bcc | string[] | nee | Ontvangers in bcc. (0–100 items) |
subject | string | nee | Onderwerpregel. (max. 998 tekens) |
html | string | nee | HTML-berichttekst. |
text | string | nee | Berichttekst in plaintext. |
reply_to_email_id | string | nee | E-mail-ID waarop dit concept antwoordt. |
thread_id | string | nee | Thread-ID waar dit concept bij hoort. |
{
"name": "update_draft",
"arguments": {
"draft_id": "dr_123",
"from": "hello@example.com",
"to": [
"owner@example.com"
],
"subject": "Invoice (updated)",
"text": "Attached."
}
}delete_draftEen concept weggooien
DESTRUCTIVE: gooit een concept weg en verwijdert de opgeslagen bijlagen permanent.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
draft_id | string | ja | Concept-ID (begint met dr_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "delete_draft",
"arguments": {
"draft_id": "dr_123"
}
}upload_attachmentEen bijlage uploaden naar een concept
Uploadt één bestand naar een concept (max. 10 bestanden en 10 MB in totaal per bericht). Geef content_base64 of een lokaal file_path op. Voor bijlagen is bij het verzenden een betaald abonnement nodig.
Geef minstens één van deze op: content_base64, file_path.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
draft_id | string | ja | Concept-ID (begint met dr_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
filename | string | nee | Bestandsnaam die de ontvanger ziet. Standaard de basisnaam van file_path. (max. 255 tekens) |
content_type | string | nee | MIME-type, bijv. application/pdf. Standaard application/octet-stream. |
content_base64 | string | nee | Standaard base64-inhoud van het bestand. |
file_path | string | nee | Absoluut pad van een lokaal bestand dat het MCP-serverproces kan lezen. |
{
"name": "upload_attachment",
"arguments": {
"draft_id": "dr_123",
"filename": "invoice.pdf",
"content_type": "application/pdf",
"file_path": "/tmp/invoice.pdf"
}
}download_attachmentEen bijlage downloaden
Downloadt een privébijlage (verzonden, ontvangen of van een concept). Geeft base64-inhoud terug, of schrijft het bestand weg als save_to_path is ingesteld (weigert te overschrijven, tenzij overwrite true is).
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
attachment_id | string | ja | Bijlage-ID (begint met att_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
save_to_path | string | nee | Optioneel absoluut lokaal pad om het bestand naartoe te schrijven in plaats van base64 terug te geven. |
overwrite | boolean | nee | Sta toe dat een bestaand bestand op save_to_path wordt vervangen. Standaard false. |
{
"name": "download_attachment",
"arguments": {
"attachment_id": "att_123",
"save_to_path": "/tmp/invoice.pdf"
}
}delete_attachmentEen bijlage verwijderen
DESTRUCTIVE: verwijdert een opgeslagen bijlage permanent (bijvoorbeeld om een bestand uit een concept te halen voordat je verstuurt).
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
attachment_id | string | ja | Bijlage-ID (begint met att_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "delete_attachment",
"arguments": {
"attachment_id": "att_123"
}
}Gehoste templates
list_templatesGehoste templates opvragen
Vraagt gehoste e-mailtemplates op met publicatiestatus en gebruik. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
lifecycle | string | nee | active (standaard), archived of all. (een van active, archived, all) |
query | string | nee | Zoeken op naam of key. (max. 120 tekens) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_templates",
"arguments": {
"lifecycle": "active"
}
}create_templateEen gehoste template aanmaken
Maakt een template met een bewerkbaar concept aan, optioneel op basis van een startsjabloon (welcome, reset, receipt of blank). Publiceer de template voordat je op key verstuurt.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | ja | Leesbare naam. (max. 120 tekens) |
key | string | nee | Stabiele verzendkey: kleine letters, cijfers en koppeltekens; begint met een letter (2–64 tekens). Wordt afgeleid van de naam als je hem weglaat. |
starter | string | nee | Startinhoud. (een van blank, welcome, reset, receipt) |
{
"name": "create_template",
"arguments": {
"name": "Account welcome",
"key": "account-welcome",
"starter": "welcome"
}
}get_templateEen template ophalen
Haalt het huidige concept van een template op (met revision), de actieve gepubliceerde release, de releasegeschiedenis en het gebruik. Accepteert een ID of key.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID (tmpl_…) of key. (max. 128 tekens) |
{
"name": "get_template",
"arguments": {
"template_id": "account-welcome"
}
}update_template_draftEen templateconcept opslaan
Slaat het bewerkbare concept van de template op met optimistic concurrency: geef de huidige revision uit get_template mee (409 betekent dat iemand anders eerder heeft opgeslagen; lees opnieuw en probeer het nog eens). Dit vervangt de conceptinhoud volledig: weggelaten velden worden leeggemaakt, dus stuur elk veld mee dat je wilt behouden. Gebruik placeholders als {{variable}}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
revision | integer | ja | Huidige conceptrevisie uit get_template. (1–…) |
name | string | nee | Templatenaam. (max. 120 tekens) |
subject_template | string | nee | Onderwerp met placeholders. (max. 998 tekens) |
preheader_template | string | nee | Voorbeeldtekst. (max. 240 tekens) |
html_template | string | nee | HTML-berichttekst met placeholders. |
text_template | string | nee | Berichttekst in plaintext met placeholders. |
from | string | nee | Standaardafzender voor verzendingen van deze template. |
reply_to | string | nee | Standaard-Reply-To. |
variables | object[] | nee | Getypeerd variabelencontract. Elk item: {key (kleine letters/underscores), label, type: text|number|url|boolean, required (standaard true), fallback, description}. |
variables[].key | string | ja | |
variables[].label | string | nee | |
variables[].type | string | nee | (een van text, number, url, boolean) |
variables[].required | boolean | nee | |
variables[].fallback | any | nee | |
variables[].description | string | nee | |
sample_data | object | nee | Voorbeeldwaarden voor voorbeelden en tests. |
{
"name": "update_template_draft",
"arguments": {
"template_id": "account-welcome",
"revision": 3,
"name": "Account welcome",
"subject_template": "Welcome, {{first_name}}",
"text_template": "Hi {{first_name}}",
"variables": [
{
"key": "first_name",
"type": "text",
"required": true
}
],
"sample_data": {
"first_name": "Asha"
}
}
}create_template_draftEen nieuw concept starten vanuit de gepubliceerde release
Maakt een nieuw bewerkbaar concept aan als kopie van de huidige gepubliceerde release (409 als er al een concept bestaat of niets is gepubliceerd).
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
{
"name": "create_template_draft",
"arguments": {
"template_id": "account-welcome"
}
}render_templateEen voorbeeld van een template renderen
Rendert de exacte serveruitvoer (onderwerp, html, tekst) voor het concept, de gepubliceerde release of een specifieke versie met de opgegeven data. Verstuurt niets. Geeft 422 met findings terug als de data het variabelencontract schendt.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
version_id | string | nee | Optioneel versie-ID; standaard het concept, daarna de gepubliceerde release. |
data | object | nee | Variabelewaarden; standaard de voorbeelddata van de versie. |
{
"name": "render_template",
"arguments": {
"template_id": "account-welcome",
"data": {
"first_name": "Asha"
}
}
}send_template_testEen testmail van een template versturen
SENDS REAL EMAIL. Send a [Test]-prefixed snapshot of the draft (or a given version) to the given recipients. Counts against usage; trial workspaces can only send to the account email or a mailbox-simulator test address.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
to | string[] | ja | Testontvangers. (1–100 items) |
from | string | nee | Afzender op een geverifieerd domein; standaard de From van de template. |
version_id | string | nee | Optioneel versie-ID. |
data | object | nee | Variabelewaarden; standaard de voorbeelddata. |
{
"name": "send_template_test",
"arguments": {
"template_id": "account-welcome",
"to": [
"owner@example.com"
]
}
}publish_templateEen templaterelease publiceren
Publiceert het huidige concept als onveranderlijke release die send_email met template.key zal gebruiken. Mislukt met 422 en findings bij validatiefouten, of met 409 als het het live variabelencontract zou breken van een template die al in productie wordt gebruikt.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
{
"name": "publish_template",
"arguments": {
"template_id": "account-welcome"
}
}archive_templateEen template archiveren
Stopt nieuwe verzendingen met deze template (de geschiedenis blijft bewaard; terug te draaien met restore_template). Elke integratie die met deze key verstuurt, begint te falen met 404.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
{
"name": "archive_template",
"arguments": {
"template_id": "account-welcome"
}
}restore_templateEen gearchiveerde template herstellen
Maakt een gearchiveerde template weer actief.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Template-ID of key. (max. 128 tekens) |
{
"name": "restore_template",
"arguments": {
"template_id": "account-welcome"
}
}Domeinen en DNS
list_domainsDomeinen opvragen
Vraagt verzenddomeinen op met een samengevatte setup_status (verified | checking | pending), de DNS-status per record en de status van inkomende e-mail. Kan traag zijn: niet-geverifieerde domeinen worden live opnieuw gecontroleerd. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_domains",
"arguments": {}
}get_domainConfiguratiegegevens van een domein ophalen
Haalt één domein op met de exacte DNS-records die je moet publiceren (type, naam, waarde), de live status van elk record volgens twee publieke resolvers, dns_issues met oplossingen en de status van inkomende e-mail.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "get_domain",
"arguments": {
"domain_id": "dom_123"
}
}add_domainEen verzenddomein toevoegen
Register a domain you control for sending. Returns the DNS records (Easy DKIM CNAMEs) the owner must publish. Does not change DNS itself. Counts against the plan's domain limit.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | ja | Kale domeinnaam, bijv. example.com of mail.example.com. (max. 253 tekens) |
default_from | string | nee | Optioneel standaard afzenderadres op dit domein. |
{
"name": "add_domain",
"arguments": {
"name": "example.com"
}
}verify_domainEen domein verifiëren
Run a live DNS and DKIM verification check now. Safe to repeat; poll every 30–60 s after DNS changes (propagation can take minutes to hours). Sending is allowed once status is verified.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "verify_domain",
"arguments": {
"domain_id": "dom_123"
}
}delete_domainEen domein verwijderen
DESTRUCTIVE: verwijdert het domein uit de workspace, inclusief de route voor inkomende e-mail. Verzendingen vanaf het domein mislukken daarna direct. DNS-records bij je DNS-provider worden niet verwijderd.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "delete_domain",
"arguments": {
"domain_id": "dom_123"
}
}get_dns_providerDNS-provider en recordhosts detecteren
Detecteert de gezaghebbende DNS-provider van het domein en geeft per record de relatieve host terug die je bij die provider moet invullen, het aanbevolen DMARC-record, richtlijnen voor de inkomende MX en of configuratie met één klik (Domain Connect) beschikbaar is.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "get_dns_provider",
"arguments": {
"domain_id": "dom_123"
}
}get_domain_connect_linkEen link voor DNS-configuratie met één klik ophalen
Maakt een ondertekende toestemmings-URL aan als get_dns_provider providers.domainConnect.available meldt. Geef die aan de mens: die opent hem en keurt de DNS-wijziging goed bij de provider. Er verandert niets totdat die goedkeurt. 409 als het niet wordt ondersteund.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "get_domain_connect_link",
"arguments": {
"domain_id": "dom_123"
}
}Inkomende e-mail
setup_inboundInkomende e-mail inschakelen voor een domein
Provision inbound receiving for a verified domain. Uses the root domain when it has no conflicting MX, otherwise inbound.<domain>. Returns the MX record the owner must publish; it does not edit DNS.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "setup_inbound",
"arguments": {
"domain_id": "dom_123"
}
}verify_inboundInkomende MX verifiëren
Controleert het inkomende MX-record opnieuw. De status wordt ready als beide publieke resolvers het zien.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "verify_inbound",
"arguments": {
"domain_id": "dom_123"
}
}list_inboxesInkomende adressen opvragen
Vraagt ontvangende adressen op, optioneel voor één domein. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | nee | Optioneel filter op domein-ID. |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_inboxes",
"arguments": {
"domain_id": "dom_123"
}
}get_inboxEen inbox ophalen
Haalt één inkomend adres op.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
inbox_id | string | ja | Inbox-ID (begint met inb_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "get_inbox",
"arguments": {
"inbox_id": "inb_123"
}
}create_inboxEen inkomend adres aanmaken
Maakt een adres zoals support@<receiving domain> aan op een domein waarvan de inkomende status ready is (voer eerst setup_inbound en verify_inbound uit). Ontvangen e-mail verschijnt in list_emails met direction in.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain_id | string | ja | Domein-ID (begint met dom_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
local_part | string | ja | Deel vóór de @, bijv. support. (max. 64 tekens) |
name | string | nee | Optionele weergavenaam. |
{
"name": "create_inbox",
"arguments": {
"domain_id": "dom_123",
"local_part": "support",
"name": "Support"
}
}update_inboxEen inbox hernoemen, inschakelen of uitschakelen
Hernoemt een inbox of zet de status op active / disabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
inbox_id | string | ja | Inbox-ID (begint met inb_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
name | string | nee | Nieuwe weergavenaam. |
status | string | nee | Nieuwe status. (een van active, disabled) |
{
"name": "update_inbox",
"arguments": {
"inbox_id": "inb_123",
"status": "disabled"
}
}set_inbox_forwardingEen inbox doorsturen naar een ander adres
SENDS REAL EMAIL bij doorsturen naar iemand anders dan de accounteigenaar: stelt in waarheen de ontvangen e-mail van een inbox wordt doorgestuurd. Het eigen adres van de eigenaar wordt direct actief; elk ander adres krijgt een bevestigingsmail en doorsturen blijft pending totdat iemand daar bevestigt. Geef forward_to: null mee om doorsturen uit te zetten. Doorgestuurde kopieën komen van het inboxadres met de oorspronkelijke afzender als Reply-To.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
inbox_id | string | ja | Inbox-ID (begint met inb_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
forward_to | string,null | ja | E-mailadres waarnaar wordt doorgestuurd, of null om doorsturen uit te zetten. (max. 254 tekens) |
{
"name": "set_inbox_forwarding",
"arguments": {
"inbox_id": "inb_123",
"forward_to": "team@example.net"
}
}delete_inboxEen inbox verwijderen
DESTRUCTIVE: verwijdert een inkomend adres. Al ontvangen e-mail blijft bewaard; nieuwe e-mail aan het adres wordt er niet meer in opgeslagen.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
inbox_id | string | ja | Inbox-ID (begint met inb_), zoals teruggegeven door een list- of create-tool. (max. 128 tekens) |
{
"name": "delete_inbox",
"arguments": {
"inbox_id": "inb_123"
}
}Deliverability, bounces en suppressies
deliverability_statsBezorgstatistieken over 30 dagen ophalen
Totalen over 30 dagen voor de hele workspace: sent, delivery, bounce, complaint, reject, open, click en deliveryRate (%).
Geen parameters.
{
"name": "deliverability_stats",
"arguments": {}
}deliverability_accountGet account delivery rates
Daily ladder, today's usage, 7-day hard-bounce and complaint rates against the promote, hold, and pause thresholds, and a per-day trend. Diagnostic text is plain text.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
days | integer | nee | (one of 7, 30, 90) |
{
"name": "deliverability_account",
"arguments": {
"days": 30
}
}deliverability_domainsGet domain delivery rates
Per sending domain: sent, delivered, hard and soft bounces, complaints, failures, rates, and an active Gmail cap or 4.7.28 backoff when one applies.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
days | integer | nee | |
domain | string | nee | |
limit | integer | nee | |
offset | integer | nee |
{
"name": "deliverability_domains",
"arguments": {
"days": 30
}
}deliverability_sendersGet sender delivery rates
Per From address: sent, delivered, hard and soft bounces, complaints, failures, and rates.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
days | integer | nee | |
domain | string | nee | |
limit | integer | nee | |
offset | integer | nee |
{
"name": "deliverability_senders",
"arguments": {
"days": 30
}
}score_emailScore an email's content
A checklist of one email's content before it is sent: 100 for a plain email with no links and no images, lower for each thing mail filters look at (a designed layout, links to another site than the sender's, link shorteners, images with few words, hidden text, capitals, an empty subject, very long HTML). Returns each finding with the points it costs and a one-line suggestion, most points first. Read-only: nothing is stored or sent. Pass the email as written; the unsubscribe footer and tracking SendHQ adds are not scored. It looks at content only: sender reputation, authentication and how recipients react decide more of where mail lands, so treat it as a checklist, not a prediction.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
subject | string | nee | The subject line. |
html | string | nee | The HTML as written, before SendHQ adds its footer or tracking. (max 2000000 chars) |
text | string | nee | The plain-text part. Compared with the HTML when both are given; scored on its own when there is no HTML. (max 2000000 chars) |
from | string | nee | The sender: an email address or a domain such as example.com. Without it, links to other sites are not judged. (max 320 chars) |
{
"name": "score_email",
"arguments": {
"from": "hello@example.com",
"subject": "Your cart is still here",
"html": "<p>Pick up where you left off.</p><p><a href=\"https://bit.ly/3xyz\">Finish checkout</a></p>"
}
}list_sender_reputationAfzenderreputatie opvragen
Reputatiestatus per exact From-adres: active, throttled (lagere daglimiet) of paused (verzendingen geven 423), met de reden en de daglimiet. Controleer dit als verzendingen mislukken met 423 of 429. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_sender_reputation",
"arguments": {}
}list_suppressionsSuppressies opvragen
Suppressielijst van de workspace: ontvangers die zijn geblokkeerd na een permanente bounce of een spamklacht. Verzendingen naar hen mislukken met 422. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_suppressions",
"arguments": {}
}remove_suppressionEen bouncesuppressie verwijderen
DESTRUCTIVE (verzwakt een veiligheidsblokkade): verwijdert een bouncesuppressie zodat het adres weer e-mail kan ontvangen. Doe dit alleen als de mens bevestigt dat het adres nu geldig is. Suppressies door klachten kunnen niet worden verwijderd (409).
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email | string | ja | Adres van de ontvanger op de suppressielijst. (max. 320 tekens) |
{
"name": "remove_suppression",
"arguments": {
"email": "fixed-mailbox@example.net"
}
}list_blocked_recipientsGeblokkeerde ontvangers opvragen
Elke ontvanger die SendHQ weigert: bounces, klachten en afmeldingen voor marketing per domein, met een overzicht per soort. Leest maximaal de 500 nieuwste. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_blocked_recipients",
"arguments": {}
}Campaigns
list_contactsList contacts
Campaigns: Newest-first contacts with their status, consent evidence, tags, custom fields, engagement (bot-filtered, estimated opens and clicks), and the lists they are subscribed to. Filter by list, status (including dormant), email/name substring (* is an email wildcard, e.g. *@example.com), tag, source, signup date, or a saved segment. Paginated: the result includes pagination {offset, limit, returned, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
list_id | string | nee | Only members of this list (lst_…). |
status | string | nee | Only contacts with this status. dormant: stopped opening and did not answer list cleanup, so broadcasts skip them. (one of subscribed, pending, unsubscribed, bounced, complained, dormant) |
query | string | nee | Email or name contains this text; * is a wildcard on the email. (max 200 chars) |
tag | string | nee | Only contacts with this tag. (max 60 chars) |
source | string | nee | How the contact was added. (one of form, api, import) |
after | string | nee | Signed up at or after this time. ISO 8601 date or date-time. (max 40 chars) |
before | string | nee | Signed up before this time. ISO 8601 date or date-time. (max 40 chars) |
segment_id | string | nee | Only contacts matching this saved segment (seg_…). |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_contacts",
"arguments": {
"status": "subscribed"
}
}create_contactAdd a contact
Campaigns: Add one contact to the workspace, optionally to lists and with tags. A subscribed contact (the default) needs consent_basis: how this person agreed to receive your email. Only add people who asked for your email. Use status: unsubscribed to record an opt-out. Addresses already suppressed or unsubscribed from the workspace are stored with that status. Fails with 409 if the email already exists.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email | string | ja | Email address. (max 320 chars) |
name | string | nee | Display name; the first word is {{first_name}}. (max 200 chars) |
fields | object | nee | Custom fields (string, number, or boolean values), e.g. {"plan": "pro"}. Usable in broadcasts as {{fields.plan}} or {{plan}}. On update, a null value removes the field. |
tags | string[] | nee | Tags to attach, e.g. ["VIP"]. Up to 50. (0–50 items) |
list_ids | string[] | nee | Lists to add the contact to (lst_…). (0–100 items) |
status | string | nee | subscribed (default, requires consent_basis) or unsubscribed. (one of subscribed, unsubscribed) |
consent_basis | string | nee | How these people agreed to receive your email, recorded as consent evidence, e.g. Signed up on acme.com/newsletter (double opt-in), exported from Mailchimp. 10-500 characters. (max 500 chars) |
{
"name": "create_contact",
"arguments": {
"email": "ada@example.net",
"name": "Ada Lovelace",
"consent_basis": "Ticked the newsletter box at checkout on acme.com"
}
}upsert_contactCreate or update a contact by email
Campaigns: Create the contact with this email, or change the one that exists: set name, timezone, and locale, merge fields, and add tags. A new contact needs consent_basis and takes the status its address already has (bounced or complained when suppressed, unsubscribed when it opted out, otherwise subscribed). An existing contact's status is never changed, so nobody is resubscribed. Unlike create_contact it does not fail when the email exists. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email | string | ja | Email address. (max 320 chars) |
name | string | nee | Display name; the first word is {{first_name}}. (max 200 chars) |
fields | object | nee | Custom fields to merge (string, number, or boolean values), e.g. {"plan": "pro"}. A null value removes a field. |
tags | string[] | nee | Tags to add, e.g. ["VIP"]. Existing tags are kept. (0–50 items) |
timezone | string | nee | IANA time zone, e.g. Europe/Paris. Automation emails respect sending hours in this zone. (max 64 chars) |
locale | string | nee | Language tag, e.g. fr or pt-br. Picks the language version of each automation email. (max 35 chars) |
consent_basis | string | nee | How this person agreed to receive your email, e.g. Created an account on acme.com and accepted product emails. Required when the email is not a contact yet. 10-500 characters. (max 500 chars) |
{
"name": "upsert_contact",
"arguments": {
"email": "ada@example.net",
"name": "Ada Lovelace",
"fields": {
"plan": "pro"
},
"timezone": "Europe/London",
"consent_basis": "Created an account on acme.com and accepted product emails"
}
}get_contactGet a contact
Campaigns: One contact by ID or email: status, consent evidence (source, basis, opt-in and confirmation times), custom fields, and subscribed lists.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
contact_id | string | ja | Contact ID (starts with ct_) or the contact's email address. (max 320 chars) |
{
"name": "get_contact",
"arguments": {
"contact_id": "ct_123"
}
}update_contactUpdate, tag, or unsubscribe a contact
Campaigns: Change a contact's name, merge custom fields (null removes one), change tags (tags replaces the whole set; add_tags and remove_tags change it), or set status to unsubscribed. A contact can never be resubscribed through the API; only the recipient can, by confirming a signup form.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
contact_id | string | ja | Contact ID (starts with ct_) or the contact's email address. (max 320 chars) |
name | string | nee | New display name. (max 200 chars) |
fields | object | nee | Custom fields (string, number, or boolean values), e.g. {"plan": "pro"}. Usable in broadcasts as {{fields.plan}} or {{plan}}. On update, a null value removes the field. |
tags | string[] | nee | Replace all of the contact's tags with these. (0–50 items) |
add_tags | string[] | nee | Tags to add. (0–50 items) |
remove_tags | string[] | nee | Tags to remove. (0–50 items) |
status | string | nee | Only unsubscribed is accepted. (one of unsubscribed) |
{
"name": "update_contact",
"arguments": {
"contact_id": "ct_123",
"fields": {
"plan": "team"
}
}
}delete_contactDelete a contact
DESTRUCTIVE: permanently delete a contact and its list memberships. Suppressions and recorded unsubscribes are kept, so the address still cannot be mailed if it is added again. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
contact_id | string | ja | Contact ID (starts with ct_) or the contact's email address. (max 320 chars) |
{
"name": "delete_contact",
"arguments": {
"contact_id": "ct_123"
}
}import_contactsImport contacts from CSV
Campaigns: Import up to 5,000 CSV rows (5 MB) per call, optionally into a list. The header row needs an email column; name (or first_name/last_name), status, and tags (separated by ; or |) are recognized and other columns become custom fields. consent_basis is required and recorded on every new contact. tags are added to every accepted row. Rows whose status says unsubscribed import as unsubscribed; existing contacts keep their status. Returns counts of accepted, created, existing, skipped (duplicates), and invalid rows with line numbers.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
csv | string | ja | The CSV file content, header row first. (max 5242880 chars) |
list_id | string | nee | Add every accepted row to this list (lst_…). |
consent_basis | string | ja | How these people agreed to receive your email, recorded as consent evidence, e.g. Signed up on acme.com/newsletter (double opt-in), exported from Mailchimp. 10-500 characters. (max 500 chars) |
tags | string[] | nee | Tags to add to every accepted row, e.g. ["imported-2026-11"]. (0–50 items) |
update_existing | boolean | nee | Merge names and fields into contacts that already exist. Their status never changes. |
{
"name": "import_contacts",
"arguments": {
"csv": "email,name\nada@example.net,Ada Lovelace\n",
"consent_basis": "Newsletter signups exported from Mailchimp (double opt-in)"
}
}list_contact_importsList contact imports
Campaigns: Recent CSV imports with their consent basis and row counts.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_contact_imports",
"arguments": {}
}bulk_update_contactsBulk update contacts
DESTRUCTIVE when action is delete (permanent) or unsubscribe (cannot be undone through the API). Apply one action to up to 10,000 contacts: the IDs in contact_ids, or everyone matching filter (the list_contacts filters). Actions: tag / untag (with tags), add_to_list / remove_from_list (with list_id), unsubscribe, delete. Adding to a list mirrors each contact's status, so nobody is resubscribed. delete needs confirm_count equal to the number of contacts it would delete: call once without it to get that count (409), confirm with the user, then repeat with it. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
action | string | ja | What to do. (one of tag, untag, add_to_list, remove_from_list, unsubscribe, delete) |
contact_ids | string[] | nee | Contact IDs (ct_…). Use this or filter. (0–10000 items) |
filter | object | nee | Everyone matching these list_contacts filters. Use this or contact_ids. |
filter.list_id | string | nee | Members of this list. |
filter.status | string | nee | Only contacts with this status. dormant: stopped opening and did not answer list cleanup, so broadcasts skip them. (one of subscribed, pending, unsubscribed, bounced, complained, dormant) |
filter.query | string | nee | Email or name contains; * is an email wildcard. (max 200 chars) |
filter.tag | string | nee | Has this tag. (max 60 chars) |
filter.source | string | nee | How the contact was added. (one of form, api, import) |
filter.after | string | nee | Signed up at or after. ISO 8601 date or date-time. (max 40 chars) |
filter.before | string | nee | Signed up before. ISO 8601 date or date-time. (max 40 chars) |
filter.segment_id | string | nee | Matches this segment. |
tags | string[] | nee | For tag and untag. (0–50 items) |
list_id | string | nee | For add_to_list and remove_from_list (lst_…). |
confirm_count | integer | nee | For delete: the number of contacts that will be deleted, from the 409 response. (0–…) |
{
"name": "bulk_update_contacts",
"arguments": {
"action": "tag",
"tags": [
"october"
],
"filter": {
"list_id": "lst_123",
"status": "subscribed"
}
}
}list_tagsList contact tags
Campaigns: The workspace's contact tags, most used first, with how many contacts carry each (up to 500). Paginated.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_tags",
"arguments": {}
}list_contact_fieldsList custom contact fields
Campaigns: Defined custom contact fields with label and type (text, number, date). Defined fields are known to check_broadcast's merge-tag check and typed in segment conditions. Contacts may also carry undefined keys. Paginated.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_contact_fields",
"arguments": {}
}set_contact_fieldDefine a custom contact field
Campaigns: Create or change a custom field definition (label and type). Values live on each contact's fields. Built-in merge tags (email, name, first_name, last_name, fields, unsubscribe_url) cannot be used as keys. A workspace may define 50 fields.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
field_key | string | ja | Field key: a lowercase letter, then up to 39 of a-z, 0-9, and _ (e.g. plan). Used in content as {{fields.plan}}. (max 40 chars) |
label | string | nee | Label shown in the dashboard. Defaults to the key. (max 80 chars) |
type | string | nee | text (default), number, or date. (one of text, number, date) |
{
"name": "set_contact_field",
"arguments": {
"field_key": "plan",
"label": "Plan",
"type": "text"
}
}delete_contact_fieldDelete a custom field definition
DESTRUCTIVE: delete a custom field definition. Values already stored on contacts are kept. Fails with 404 when the field is not defined. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
field_key | string | ja | Field key: a lowercase letter, then up to 39 of a-z, 0-9, and _ (e.g. plan). Used in content as {{fields.plan}}. (max 40 chars) |
{
"name": "delete_contact_field",
"arguments": {
"field_key": "plan"
}
}list_segmentsList segments
Campaigns: Saved segments with count (subscribed, non-dormant contacts in the workspace that match now) and fields, the condition fields and operators each accepts. Paginated.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_segments",
"arguments": {}
}get_segmentGet a segment
Campaigns: One segment with its conditions and live count.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
segment_id | string | ja | Segment ID (starts with seg_), as returned by list_segments or create_segment. (max 128 chars) |
{
"name": "get_segment",
"arguments": {
"segment_id": "seg_123"
}
}preview_segmentPreview segment conditions
Campaigns: Count and sample (up to 5) the subscribed, non-dormant contacts that match conditions without saving them. Read-only; use it to check conditions before create_segment.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
match | string | nee | all (default): every condition must match. any: at least one. (one of all, any) |
conditions | object[] | nee | Up to 20 conditions. Opened and clicked use bot-filtered, estimated engagement. (0–20 items) |
conditions[].field | string | ja | tag, list, status, source, email, name, signed_up, opened, clicked, opens, sends_without_open, country, or a custom field as fields.<key> (or field together with key). (max 48 chars) |
conditions[].key | string | nee | Custom field key when field is field. (max 40 chars) |
conditions[].op | string | ja | tag: has, not_has. list: in, not_in (a list ID). status: is, is_not (subscribed, pending, unsubscribed, bounced, complained, dormant). source: is, is_not (form, api, import). email: contains, not_contains, ends_with. name: is_set, not_set. signed_up: before, after (YYYY-MM-DD), in_last_days, not_in_last_days. opened / clicked: in_last_days, not_in_last_days, ever, never. opens / sends_without_open: gte, lte. country: is, is_not (two-letter code). Custom fields: equals, not_equals, contains, gt, lt, before, after, is_set, not_set. (one of has, not_has, in, not_in, is, is_not, contains, not_contains, ends_with, is_set, not_set, before, after, in_last_days, not_in_last_days, ever, never, gte, lte, equals, not_equals, gt, lt) |
conditions[].value | string,number | nee | Required except for is_set, not_set, ever, and never. A number of days for in_last_days / not_in_last_days, a number for gte, lte, gt, lt, a date (YYYY-MM-DD) for before / after. |
{
"name": "preview_segment",
"arguments": {
"match": "all",
"conditions": [
{
"field": "tag",
"op": "has",
"value": "VIP"
},
{
"field": "opened",
"op": "in_last_days",
"value": 90
}
]
}
}create_segmentCreate a segment
Campaigns: Save a segment: up to 20 conditions joined by match. Use it as a broadcast's audience.segment_id, as list_contacts segment_id, or in bulk_update_contacts filters. A workspace may have 200 segments.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | ja | Segment name. (max 120 chars) |
match | string | nee | all (default): every condition must match. any: at least one. (one of all, any) |
conditions | object[] | nee | Up to 20 conditions. Opened and clicked use bot-filtered, estimated engagement. (0–20 items) |
conditions[].field | string | ja | tag, list, status, source, email, name, signed_up, opened, clicked, opens, sends_without_open, country, or a custom field as fields.<key> (or field together with key). (max 48 chars) |
conditions[].key | string | nee | Custom field key when field is field. (max 40 chars) |
conditions[].op | string | ja | tag: has, not_has. list: in, not_in (a list ID). status: is, is_not (subscribed, pending, unsubscribed, bounced, complained, dormant). source: is, is_not (form, api, import). email: contains, not_contains, ends_with. name: is_set, not_set. signed_up: before, after (YYYY-MM-DD), in_last_days, not_in_last_days. opened / clicked: in_last_days, not_in_last_days, ever, never. opens / sends_without_open: gte, lte. country: is, is_not (two-letter code). Custom fields: equals, not_equals, contains, gt, lt, before, after, is_set, not_set. (one of has, not_has, in, not_in, is, is_not, contains, not_contains, ends_with, is_set, not_set, before, after, in_last_days, not_in_last_days, ever, never, gte, lte, equals, not_equals, gt, lt) |
conditions[].value | string,number | nee | Required except for is_set, not_set, ever, and never. A number of days for in_last_days / not_in_last_days, a number for gte, lte, gt, lt, a date (YYYY-MM-DD) for before / after. |
{
"name": "create_segment",
"arguments": {
"name": "Engaged pro customers",
"conditions": [
{
"field": "fields.plan",
"op": "equals",
"value": "pro"
},
{
"field": "opened",
"op": "in_last_days",
"value": 90
}
]
}
}update_segmentUpdate a segment
Campaigns: Rename a segment or change match or conditions (which replaces the whole list). Broadcasts using it pick up the change when they start sending.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
segment_id | string | ja | Segment ID (starts with seg_), as returned by list_segments or create_segment. (max 128 chars) |
name | string | nee | Segment name. (max 120 chars) |
match | string | nee | all (default): every condition must match. any: at least one. (one of all, any) |
conditions | object[] | nee | Up to 20 conditions. Opened and clicked use bot-filtered, estimated engagement. (0–20 items) |
conditions[].field | string | ja | tag, list, status, source, email, name, signed_up, opened, clicked, opens, sends_without_open, country, or a custom field as fields.<key> (or field together with key). (max 48 chars) |
conditions[].key | string | nee | Custom field key when field is field. (max 40 chars) |
conditions[].op | string | ja | tag: has, not_has. list: in, not_in (a list ID). status: is, is_not (subscribed, pending, unsubscribed, bounced, complained, dormant). source: is, is_not (form, api, import). email: contains, not_contains, ends_with. name: is_set, not_set. signed_up: before, after (YYYY-MM-DD), in_last_days, not_in_last_days. opened / clicked: in_last_days, not_in_last_days, ever, never. opens / sends_without_open: gte, lte. country: is, is_not (two-letter code). Custom fields: equals, not_equals, contains, gt, lt, before, after, is_set, not_set. (one of has, not_has, in, not_in, is, is_not, contains, not_contains, ends_with, is_set, not_set, before, after, in_last_days, not_in_last_days, ever, never, gte, lte, equals, not_equals, gt, lt) |
conditions[].value | string,number | nee | Required except for is_set, not_set, ever, and never. A number of days for in_last_days / not_in_last_days, a number for gte, lte, gt, lt, a date (YYYY-MM-DD) for before / after. |
{
"name": "update_segment",
"arguments": {
"segment_id": "seg_123",
"name": "Pro customers"
}
}delete_segmentDelete a segment
DESTRUCTIVE: delete a saved segment. Contacts are not affected. Fails with 409 while a sending or scheduled broadcast uses it. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
segment_id | string | ja | Segment ID (starts with seg_), as returned by list_segments or create_segment. (max 128 chars) |
{
"name": "delete_segment",
"arguments": {
"segment_id": "seg_123"
}
}list_listsList contact lists
Campaigns: Contact lists with subscribed, pending, and unsubscribed counts and their hosted signup form settings.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_lists",
"arguments": {}
}create_listCreate a list
Campaigns: Create a contact list. Set form_enabled to publish a hosted double opt-in signup form (its URL is in form.url); form_from is the sender, on a verified domain, of the confirmation email, and redirect_url is an optional https page shown after confirming. welcome sends one welcome email when someone confirms. site publishes a public newsletter site at https://sendhq.cc/n/<slug> with the signup form, sent issues, and RSS.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | ja | List name, shown on the signup form. (max 200 chars) |
description | string | nee | Short description shown on the signup form. (max 500 chars) |
form_enabled | boolean | nee | Publish the hosted signup form. |
form_from | string | nee | Sender of signup confirmation emails, e.g. Acme <news@example.com>, on a verified domain. (max 320 chars) |
redirect_url | string | nee | https page to open after a signup is confirmed. (max 500 chars) |
welcome | object | nee | Welcome email sent once, from form_from, when someone confirms a signup. Needs subject and html or markdown when enabled. |
welcome.enabled | boolean | nee | Send it. |
welcome.subject | string | nee | Subject; merge tags allowed. (max 300 chars) |
welcome.html | string | nee | HTML body; merge tags allowed. (max 500000 chars) |
welcome.markdown | string | nee | Markdown body instead of html, rendered with the workspace design. (max 200000 chars) |
site | object | nee | Public newsletter site at https://sendhq.cc/n/<slug>: a signup form, every issue sent with web.enabled, and an RSS feed at /n/<slug>/feed.xml. Needs the signup form on. A reserved or taken slug fails with 409. |
site.enabled | boolean | nee | Publish the site. |
site.slug | string,null | nee | Address after /n/ (3-48 characters, a-z, 0-9, -). Defaults to the list name. (max 48 chars) |
site.title | string,null | nee | Site title. Defaults to the list name. (max 120 chars) |
site.description | string,null | nee | Short description under the title. (max 300 chars) |
site.accent | string,null | nee | Accent color, e.g. #0a7d4f. |
{
"name": "create_list",
"arguments": {
"name": "Product updates"
}
}get_listGet a list
Campaigns: One list with member counts and signup form settings.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
list_id | string | ja | List ID (starts with lst_), as returned by a list or create tool. (max 128 chars) |
{
"name": "get_list",
"arguments": {
"list_id": "lst_123"
}
}update_listUpdate a list
Campaigns: Rename a list, change its description, or change its hosted signup form, welcome email, or newsletter site. Omitted keys inside welcome and site keep their value.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
list_id | string | ja | List ID (starts with lst_), as returned by a list or create tool. (max 128 chars) |
name | string | nee | New name. (max 200 chars) |
description | string | nee | New description. (max 500 chars) |
form_enabled | boolean | nee | Publish or unpublish the hosted signup form. |
form_from | string | nee | Sender of signup confirmation emails, on a verified domain. (max 320 chars) |
redirect_url | string | nee | https page to open after a signup is confirmed. (max 500 chars) |
welcome | object | nee | Welcome email sent once, from form_from, when someone confirms a signup. Needs subject and html or markdown when enabled. |
welcome.enabled | boolean | nee | Send it. |
welcome.subject | string | nee | Subject; merge tags allowed. (max 300 chars) |
welcome.html | string | nee | HTML body; merge tags allowed. (max 500000 chars) |
welcome.markdown | string | nee | Markdown body instead of html, rendered with the workspace design. (max 200000 chars) |
site | object | nee | Public newsletter site at https://sendhq.cc/n/<slug>: a signup form, every issue sent with web.enabled, and an RSS feed at /n/<slug>/feed.xml. Needs the signup form on. A reserved or taken slug fails with 409. |
site.enabled | boolean | nee | Publish the site. |
site.slug | string,null | nee | Address after /n/ (3-48 characters, a-z, 0-9, -). Defaults to the list name. (max 48 chars) |
site.title | string,null | nee | Site title. Defaults to the list name. (max 120 chars) |
site.description | string,null | nee | Short description under the title. (max 300 chars) |
site.accent | string,null | nee | Accent color, e.g. #0a7d4f. |
{
"name": "update_list",
"arguments": {
"list_id": "lst_123",
"form_enabled": false
}
}delete_listDelete a list
DESTRUCTIVE: delete a list and its memberships. The contacts themselves are kept. Fails with 409 while a broadcast to the list is sending. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
list_id | string | ja | List ID (starts with lst_), as returned by a list or create tool. (max 128 chars) |
{
"name": "delete_list",
"arguments": {
"list_id": "lst_123"
}
}add_list_contactsAdd contacts to a list
Campaigns: Add up to 500 existing contacts to a list by ID or email. Subscribed contacts join subscribed; others join in their current state. Unknown references come back in notFound.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
list_id | string | ja | List ID (starts with lst_), as returned by a list or create tool. (max 128 chars) |
contact_ids | string[] | nee | Contact IDs (ct_…). (0–500 items) |
emails | string[] | nee | Contact email addresses. (0–500 items) |
{
"name": "add_list_contacts",
"arguments": {
"list_id": "lst_123",
"emails": [
"ada@example.net"
]
}
}remove_list_contactRemove a contact from a list
DESTRUCTIVE: remove one contact from a list. The contact and its status are kept. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
list_id | string | ja | List ID (starts with lst_), as returned by a list or create tool. (max 128 chars) |
contact_id | string | ja | Contact ID (starts with ct_) or the contact's email address. (max 320 chars) |
{
"name": "remove_list_contact",
"arguments": {
"list_id": "lst_123",
"contact_id": "ct_123"
}
}list_broadcastsList broadcasts
Campaigns: Newest-first broadcasts with their status. Paginated: the result includes pagination.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
status | string | nee | Only broadcasts with this status. (one of draft, sending, sent, cancelled, failed) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_broadcasts",
"arguments": {}
}create_broadcastCreate a broadcast draft
Campaigns: Create a draft broadcast to one list. Content is html and/or text, markdown, a block document in content, or a published hosted template. Raw content supports merge tags: {{first_name}}, {{name}}, {{email}}, {{fields.plan}}, with fallbacks like {{first_name | there}}. audience narrows it to a segment and/or a number of people (most engaged first with order: engaged); tracking turns open and click tracking off; web publishes it on the list's newsletter site once sent. Nothing is sent until send_broadcast or schedule_broadcast; run check_broadcast and send_broadcast_test first.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | nee | Internal name. Defaults to the subject. (max 200 chars) |
list_id | string | nee | The list to send to (lst_…). |
from | string | nee | Sender on a verified domain, e.g. Acme <news@example.com>. (max 320 chars) |
reply_to | string | nee | Reply-To address. (max 320 chars) |
subject | string | nee | Subject line; merge tags allowed. (max 998 chars) |
preview_text | string | nee | Inbox preview text shown after the subject. (max 300 chars) |
html | string | nee | HTML body; merge tags allowed and escaped. |
text | string | nee | Plain-text body; merge tags allowed. |
template | object | nee | A published hosted template instead of subject/html/text. Template variables are filled from the contact's name, email, and fields. |
template.id | string | nee | |
template.key | string | nee | |
template.version_id | string | nee | |
markdown | string | nee | Markdown body instead of html: converted to a block document and rendered with the workspace design (get_newsletter_settings). Merge tags allowed. Not combinable with html or content. (max 1000000 chars) |
content | object,null | nee | Block document ({"type": "doc", "content": [...]}, the dashboard editor's format: paragraph, heading, bulletList, orderedList, blockquote, image, button, callout, horizontalRule, codeBlock). Rendered with the workspace design unless html is also sent. |
editor | string | nee | Which editor the dashboard opens: html or blocks. Set automatically for markdown and content. (one of html, blocks) |
audience | object | nee | Who gets it, within the list. Subscribed, non-dormant members only. |
audience.segment_id | string,null | nee | Only list members matching this segment (seg_…), or null for the whole list. |
audience.order | string | nee | With a limit: signup (default) or engaged (most engaged first). (one of signup, engaged) |
audience.limit | integer,null | nee | Send to at most this many people (send_broadcast_to_more sends to more later), or null for everyone. (1–10000000) |
tracking | object | nee | Open and click tracking, both on by default. Opens are estimates (bot-filtered pixel loads), never proof that someone read the email. |
tracking.opens | boolean | nee | Add an open pixel. |
tracking.clicks | boolean | nee | Rewrite links to signed SendHQ redirects (the unsubscribe link never is). |
web | object | nee | Publish this issue on the list's newsletter site (see create_list site) once it is sent. |
web.enabled | boolean | nee | Publish it. |
web.slug | string,null | nee | Issue address; defaults to the subject. (max 100 chars) |
web.pinned | boolean | nee | Keep it at the top of the site. |
{
"name": "create_broadcast",
"arguments": {
"list_id": "lst_123",
"from": "news@example.com",
"subject": "October update",
"markdown": "Hi {{first_name | there}}, here's what shipped.",
"audience": {
"order": "engaged",
"limit": 1000
}
}
}get_broadcastGet a broadcast
Campaigns: One broadcast with its content and, once sending, recipient totals (queued, sending, sent, held, skipped, failed). While a limit or reputation pause holds delivery, lastError explains why and nextAttemptAt says when it resumes.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "get_broadcast",
"arguments": {
"broadcast_id": "bc_123"
}
}update_broadcastEdit a draft broadcast
Campaigns: Change any field of an unscheduled draft broadcast (content, audience, tracking, web). A scheduled draft must be unscheduled first (unschedule_broadcast); sent or sending broadcasts cannot be edited.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
name | string | nee | Internal name. (max 200 chars) |
list_id | string | nee | The list to send to. |
from | string | nee | Sender on a verified domain. (max 320 chars) |
reply_to | string | nee | Reply-To address. (max 320 chars) |
subject | string | nee | Onderwerpregel. (max. 998 tekens) |
preview_text | string | nee | Inbox preview text. (max 300 chars) |
html | string | nee | HTML-berichttekst. |
text | string | nee | Berichttekst in plaintext. |
template | object,null | nee | A published hosted template, or null to remove it. |
markdown | string | nee | Markdown body instead of html: converted to a block document and rendered with the workspace design (get_newsletter_settings). Merge tags allowed. Not combinable with html or content. (max 1000000 chars) |
content | object,null | nee | Block document ({"type": "doc", "content": [...]}, the dashboard editor's format: paragraph, heading, bulletList, orderedList, blockquote, image, button, callout, horizontalRule, codeBlock). Rendered with the workspace design unless html is also sent. |
editor | string | nee | Which editor the dashboard opens: html or blocks. Set automatically for markdown and content. (one of html, blocks) |
audience | object | nee | Who gets it, within the list. Subscribed, non-dormant members only. |
audience.segment_id | string,null | nee | Only list members matching this segment (seg_…), or null for the whole list. |
audience.order | string | nee | With a limit: signup (default) or engaged (most engaged first). (one of signup, engaged) |
audience.limit | integer,null | nee | Send to at most this many people (send_broadcast_to_more sends to more later), or null for everyone. (1–10000000) |
tracking | object | nee | Open and click tracking, both on by default. Opens are estimates (bot-filtered pixel loads), never proof that someone read the email. |
tracking.opens | boolean | nee | Add an open pixel. |
tracking.clicks | boolean | nee | Rewrite links to signed SendHQ redirects (the unsubscribe link never is). |
web | object | nee | Publish this issue on the list's newsletter site (see create_list site) once it is sent. |
web.enabled | boolean | nee | Publish it. |
web.slug | string,null | nee | Issue address; defaults to the subject. (max 100 chars) |
web.pinned | boolean | nee | Keep it at the top of the site. |
{
"name": "update_broadcast",
"arguments": {
"broadcast_id": "bc_123",
"subject": "October product update"
}
}delete_broadcastDelete a draft broadcast
DESTRUCTIVE: permanently delete a draft broadcast. Broadcasts that were sent cannot be deleted. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "delete_broadcast",
"arguments": {
"broadcast_id": "bc_123"
}
}send_broadcastSend a broadcast
SENDS REAL EMAIL to the broadcast's audience: every subscribed, non-dormant member of its list, narrowed by its segment and limit. Only call it when the user asked to send this broadcast now. Each message goes through the normal checks (verified domain, marketing plan, suppressions, unsubscribes, reputation, daily and monthly limits) and carries one-click unsubscribe from this list; members that cannot be mailed are skipped. Each contact is sent at most once. Delivery continues in the background: poll get_broadcast for totals and get_broadcast_report for engagement. A scheduled broadcast fails with 409 until unscheduled. Unpaid workspaces (integration trial) can send only to the account email. Pass idempotency_key so a retry cannot start the send twice. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
idempotency_key | string | nee | Idempotency-Key-header (max. 200 tekens). Hergebruik die alleen om exact dit request opnieuw te proberen. (max. 200 tekens) |
{
"name": "send_broadcast",
"arguments": {
"broadcast_id": "bc_123",
"idempotency_key": "october-update"
}
}cancel_broadcastCancel a broadcast
DESTRUCTIVE: stop a draft or sending broadcast for good. Recipients not yet sent are marked skipped; messages already handed to the provider are not recalled. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "cancel_broadcast",
"arguments": {
"broadcast_id": "bc_123"
}
}list_broadcast_recipientsList broadcast recipients
Campaigns: Per-recipient outcomes and engagement of a broadcast: queued, sending, sent, held, skipped (with the reason), or failed (with the error), the inbox provider, delivered/opened/clicked/bounced/complained/unsubscribed times, and the email ID to inspect delivery events with list_email_events. Filter by outcome, by activity (who opened, clicked, did not open, ...), or by email. Opens are bot-filtered estimates, never proof of reading. Paginated.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
status | string | nee | Only recipients with this outcome. (one of queued, sending, sent, held, skipped, failed) |
activity | string | nee | Only recipients who did this. (one of opened, clicked, not_opened, not_delivered, bounced, complained, unsubscribed) |
query | string | nee | Recipient email contains this text. (max 200 chars) |
include | string | nee | links adds the links each recipient clicked (implied by activity: clicked). (one of links) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_broadcast_recipients",
"arguments": {
"broadcast_id": "bc_123",
"status": "failed"
}
}check_broadcastRun a broadcast's pre-send checks
Campaigns: The review list shown before sending: sender verification, subject, preview text, content, audience size, size against Gmail's 102 KB clipping limit, postal address, merge tags without data or fallback, empty or shortened links, image descriptions, placeholder text, spam-prone wording, the trial's own-address rule, and whether a test was sent. ready is false while any check has level block; schedule_broadcast refuses then. Fix warn items or tell the user about them.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "check_broadcast",
"arguments": {
"broadcast_id": "bc_123"
}
}send_broadcast_testSend a broadcast test
SENDS REAL EMAIL: a copy of the draft marked [Test] to up to 5 addresses (default: the saved test recipients, or the account email), with merge tags filled from contact_id or a sample contact. Never goes to the list. Only send to addresses the user gave or owns. Limited to 100 test sends a day. Template broadcasts are tested with send_template_test. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
to | string[] | nee | Test recipients (up to 5). (1–5 items) |
contact_id | string | nee | Fill merge tags from this contact (ct_…). (max 320 chars) |
remember | boolean | nee | Save to as the default test recipients. |
{
"name": "send_broadcast_test",
"arguments": {
"broadcast_id": "bc_123",
"to": [
"owner@example.com"
]
}
}schedule_broadcastSchedule a broadcast
SENDS REAL EMAIL at scheduled_at to the broadcast's audience, with the same checks as send_broadcast. Only call it when the user asked to send this broadcast at that time. The pre-send checks run now (422 with checks if one blocks). It starts within about a minute of the time; if it can no longer send then, it returns to a draft with the reason in lastError. A scheduled draft cannot be edited until unschedule_broadcast. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
scheduled_at | string | ja | When to send: ISO 8601 date-time with a timezone, at least a minute and at most a year ahead, e.g. 2026-11-10T09:00:00Z. (max 40 chars) |
{
"name": "schedule_broadcast",
"arguments": {
"broadcast_id": "bc_123",
"scheduled_at": "2026-11-10T09:00:00Z"
}
}unschedule_broadcastUnschedule a broadcast
Campaigns: Return a scheduled broadcast to an editable draft so it does not send. Fails with 409 when it is not scheduled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "unschedule_broadcast",
"arguments": {
"broadcast_id": "bc_123"
}
}duplicate_broadcastDuplicate a broadcast
Campaigns: Copy any broadcast (draft, sent, or cancelled) into a new draft named <name> (copy) with the same list, sender, content, audience, and tracking settings. Nothing is sent.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "duplicate_broadcast",
"arguments": {
"broadcast_id": "bc_123"
}
}send_broadcast_to_moreSend a broadcast to more people
SENDS REAL EMAIL: sends a sent or sending broadcast to up to limit more people in its audience who have not received it (the rest of a limited audience, or people who joined since), in its audience order. Only call it when the user asked for this. Same checks as send_broadcast; each contact still gets it at most once. Fails with 422 when everyone already got it. Pass idempotency_key so a retry cannot add people twice. Part of Campaigns.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
limit | integer | ja | How many more people at most. (1–10000000) |
idempotency_key | string | nee | Idempotency-Key-header (max. 200 tekens). Hergebruik die alleen om exact dit request opnieuw te proberen. (max. 200 tekens) |
{
"name": "send_broadcast_to_more",
"arguments": {
"broadcast_id": "bc_123",
"limit": 500,
"idempotency_key": "october-update-more-1"
}
}get_broadcast_reportGet a broadcast report
Campaigns: Engagement for a sending or sent broadcast: unique and total opens and clicks, bounces, complaints, and unsubscribes with rates in percent, the same per inbox provider, clicks per link, first opens and clicks by hour, and the average of the previous five broadcasts. Opens are estimates: automated requests (scanners, link previews, privacy prefetching) are counted only in machine. Never claim that a person read the email. Fails with 409 for a draft.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
broadcast_id | string | ja | Broadcast ID (starts with bc_), as returned by a list or create tool. (max 128 chars) |
{
"name": "get_broadcast_report",
"arguments": {
"broadcast_id": "bc_123"
}
}get_newsletter_settingsGet newsletter settings
Campaigns: The postal address added to every marketing email footer, the design (accent color, font, alignment) used for Markdown and block content, list cleanup settings, and default test recipients.
Geen parameters.
{
"name": "get_newsletter_settings",
"arguments": {}
}update_newsletter_settingsUpdate newsletter settings
Campaigns: Change the postal address (required in marketing email by CAN-SPAM and CASL), design, list cleanup, or default test recipients. Omitted keys keep their value. List cleanup is on by default and sends email automatically: a subscriber who got afterSends broadcasts in a row without opening or clicking and has been quiet for quietDays gets one "still want these?" email; a week later those who did not confirm become dormant (kept, but skipped by broadcasts). Confirm with the user before turning it on or changing its email.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
postal_address | string | nee | Sender's postal address for the footer. Empty string removes it. (max 300 chars) |
design | object | nee | Rendering design for Markdown and block content. |
design.accentColor | string,null | nee | Hex color like #0a7d4f, or null for the default. |
design.font | string | nee | Font family. (one of sans, serif, mono) |
design.align | string | nee | Text alignment. (one of left, center) |
cleanup | object | nee | List cleanup of readers who stopped opening. |
cleanup.enabled | boolean | nee | Turn list cleanup on or off. |
cleanup.afterSends | integer | nee | Broadcasts in a row without an open or click (3-50). (3–50) |
cleanup.quietDays | integer | nee | Days without engagement (30-730). (30–730) |
cleanup.subject | string,null | nee | Subject of the cleanup email; merge tags allowed. (max 200 chars) |
cleanup.body | string,null | nee | Body text of the cleanup email. (max 2000 chars) |
cleanup.from | string,null | nee | Sender on a verified domain. Defaults to the last sent broadcast's sender. (max 320 chars) |
test_recipients | string[] | nee | Default addresses for send_broadcast_test (up to 5). (0–5 items) |
{
"name": "update_newsletter_settings",
"arguments": {
"postal_address": "Acme Inc., 1 Main St, Springfield",
"design": {
"accentColor": "#0a7d4f"
}
}
}get_campaign_overviewGet campaign overview
Campaigns: Subscriber growth and recent results for the last days (7-365, default 30): active, dormant, and pending subscribers, joined and left, a daily series, and the six latest broadcasts with open and click rates (bot-filtered estimates) and their average.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
days | integer | nee | Window in days, 7 to 365. Defaults to 30. (7–365) |
{
"name": "get_campaign_overview",
"arguments": {
"days": 30
}
}list_uploaded_imagesList uploaded images
Campaigns: The workspace's 60 most recent editor image uploads with their public URLs (https://sendhq.cc/i/<id>), to reuse in broadcast HTML, Markdown, or image blocks. Uploading needs the dashboard or the REST API (raw image body). Paginated.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_uploaded_images",
"arguments": {}
}Automations, events, and sending limits
track_eventRecord something a contact did
SENDS REAL EMAIL later, when an automation is listening: the contact enters every automation that is on and starts on this event, and that automation then emails them on its schedule, within the workspace's sending limits and hours. Only record what the person really did. In order: the contact changes in contact and the event are saved; open enrolments whose automation names the event as its goal end as converted, and ones that list it as a stop event end; then the contact enters the automations that start on it, unless already in them or reentry forbids it. A contact that is unsubscribed, bounced, or complained is recorded and can leave automations but never enters one. A new contact needs contact.consent_basis. Pass dedupe_key so a retry changes nothing and returns the first result. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
email | string | ja | The contact's email address. (max 320 chars) |
event | string | ja | What they did: a lowercase letter, then a-z, 0-9, and _ (e.g. checkout_started). Names starting email. are reserved. (max 64 chars) |
properties | object | nee | Up to 50 values (string, number, or boolean; strings are cut at 500 characters), e.g. {"plan": "pro"}. Usable in the automation's emails as merge tags such as {{ plan }}. The names email, name, first_name, last_name, and fields are reserved. |
occurred_at | string | nee | When it happened, ISO 8601 with a time zone. Defaults to now; may not be in the future. The automation's emails are timed from it. (max 40 chars) |
dedupe_key | string | nee | Stable ID for this event (max 200 chars). A second call with the same key records nothing and returns the first result. (max 200 chars) |
contact | object | nee | Changes to the contact, applied with the event. |
contact.name | string | nee | Display name. (max 200 chars) |
contact.fields | object | nee | Custom fields to merge (string, number, or boolean values), e.g. {"plan": "pro"}. A null value removes a field. |
contact.timezone | string | nee | IANA time zone, e.g. Europe/Paris. Automation emails respect sending hours in this zone. (max 64 chars) |
contact.locale | string | nee | Language tag, e.g. fr or pt-br. Picks the language version of each automation email. (max 35 chars) |
contact.consent_basis | string | nee | How this person agreed to receive your email, e.g. Created an account on acme.com and accepted product emails. Required when the email is not a contact yet. 10-500 characters. (max 500 chars) |
{
"name": "track_event",
"arguments": {
"email": "ada@example.net",
"event": "checkout_started",
"properties": {
"plan": "pro"
},
"dedupe_key": "checkout_8f3a"
}
}list_automationsList automations
Automations: Every automation in priority order with its status (draft, on, or off), how many emails it has, and totals for the last 30 days (entered, sent, delivered, opened, clicked, converted, bounced, complained, unsubscribed, held). held counts each time an email was made to wait by the sending limits, the sending hours, or the automation's daily cap. Each automation carries domain, the domain of its from_address (null while it has no sender). domain narrows the list to the automations that send from one domain (none: those with no sender yet); domains always lists every sender domain of the workspace, in alphabetical order, with how many automations each has. Email bodies are not included; use get_automation. For other date ranges and daily numbers use get_automation_report. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
domain | string | nee | Only the automations that send from this domain: the exact domain of their from_address (e.g. example.com), or none for automations with no sender yet. (max 253 chars) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_automations",
"arguments": {
"domain": "example.com"
}
}get_automationGet an automation
Automations: One automation with its emails in order and their language versions, how many people are in it now, and overlap: the other automations that are on and currently have the same people in them, with goes_first true for one that ranks above this automation (the shared people get its emails first and wait in this one). to_fill lists what must still be filled in before it can be turned on: placeholders of the template library left in its emails, and workspace names they print that are blank. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
{
"name": "get_automation",
"arguments": {
"automation_key": "checkout-recovery"
}
}create_automationCreate an automation
Automations: Create a timed sequence of emails for one kind of person, as a draft. To start from a ready-made email instead (welcome, onboarding, trial, abandoned checkout, failed payment, winback and more), use use_automation_template. Nothing is sent until set_automation_status turns it on. key is its address and cannot be changed. entry says how people enter, exit_rules when they leave, and steps are the emails, each due offset_seconds after the person entered. from_address must be on a verified domain. Fails with 409 when the key is taken. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
key | string | ja | Address of the automation: 1-63 characters of a-z, 0-9, and - (e.g. checkout-recovery). (max 63 chars) |
name | string | ja | Name shown in the dashboard. (max 200 chars) |
audience_label | string | nee | Who this is for, in plain words, e.g. Started checkout and left. (max 200 chars) |
goal_label | string | nee | What converting means, in a word or two, e.g. paid. (max 80 chars) |
entry | object | nee | How people enter. {type: "event", event} starts on an event recorded with track_event; {type: "manual"} only through enroll_contact. bucket (with segment_id) and date_field (with field) are stored, but nobody enters through them automatically yet. reentry: never (default) or after_end. |
entry.type | string | ja | Entry type. (one of event, bucket, date_field, manual) |
entry.event | string | nee | Event name for an event entry, e.g. checkout_started. |
entry.segment_id | string | nee | Segment ID (seg_…) for a bucket entry. (max 128 chars) |
entry.field | string | nee | Contact field key for a date_field entry. (max 40 chars) |
entry.reentry | string | nee | Whether someone who finished may enter again. (one of never, after_end) |
exit_rules | object | nee | When people leave. goal_event ends the enrolment as converted and credits the latest email sent within attribution_days before it. Each of stop_events ends it without a conversion. An automation with no goal must say so with no_goal: true. Sent whole: it replaces the current rules. |
exit_rules.goal_event | string,null | nee | Event that counts as converting, e.g. payment_completed. |
exit_rules.no_goal | boolean | nee | True when this automation deliberately has no goal. |
exit_rules.stop_events | string[] | nee | Events that take a person out, e.g. ["account_closed"]. (0–20 items) |
exit_rules.attribution_days | integer | nee | Days before the goal within which an email earns the conversion. Default 14. (1–90) |
settings | object | nee | Per-automation settings. Omitted keys keep their value. |
settings.exempt_from_hold | boolean | nee | Skip the workspace's per-person limits (max_emails and min_gap_hours) for this automation. The sending hours still apply, and its emails still count toward the limits of other automations. |
settings.daily_send_cap | integer,null | nee | At most this many emails a day from this automation, counted by the day of the workspace's default_timezone; emails over it wait until the next day. null for no cap. (1–…) |
settings.daily_entry_cap | integer,null | nee | Stored for bucket entries, which are not started automatically yet. It does not limit people entering by event or through enroll_contact. null for no cap. (1–…) |
settings.holdout_pct | number | nee | Percent of people who enter but are sent nothing, to measure what the emails change (0-100). (0–100) |
settings.stale_days | integer | nee | An email more than this many days overdue is skipped instead of sent late. Default 4. (1–365) |
settings.resume_after_days | integer | nee | How long a waiting enrolment waits after the automation ahead of it ends. Default 3. (0–365) |
position | integer | nee | Priority. While one person is in several automations that are on, only the one with the lowest position emails them; the others wait and resume resume_after_days after it ends. (0–100000) |
from_name | string | nee | Sender display name, e.g. Acme. (max 120 chars) |
from_address | string | nee | Sender address on a verified workspace domain (see list_sending_identities). (max 320 chars) |
reply_to | string | nee | Reply-To address. (max 320 chars) |
steps | object[] | nee | The emails, in order. position defaults to the place in this list. (0–50 items) |
steps[].position | integer | nee | Position of the email in the automation, 1 to 50. (1–50) |
steps[].subject | string | nee | Subject line. Merge tags such as {{ first_name | there }} are filled per contact. (max 998 chars) |
steps[].preheader | string | nee | Inbox preview line. (max 300 chars) |
steps[].content | object | nee | Block document ({type: "doc", content: [...]}), as the dashboard editor stores it. Sent without html, it is rendered with the workspace design. On an email built in the dashboard's drag-and-drop builder (editor design) it is the builder's project instead: opaque, never write one by hand, and send it back only unchanged together with its html. |
steps[].html | string | nee | HTML body. The unsubscribe footer is added automatically. |
steps[].text | string | nee | Berichttekst in plaintext. |
steps[].editor | string | nee | How the email is made: blocks (the dashboard's writing editor, the default), html (your own HTML) or design (the dashboard's drag-and-drop builder). Only the builder makes a design; to send a designed email yourself, send html with editor html. (one of blocks, html, design) |
steps[].offset_seconds | integer | nee | When the email is due, in seconds after the moment the person entered (3600 = one hour, 86400 = one day). May be negative for emails that lead up to a date. When several emails are due at once, only the latest is sent and the earlier ones are skipped. (-31622400–31622400) |
steps[].skip_if_empty | string[] | nee | Merge keys, e.g. ["fields.plan"]. The email is skipped for a contact where any of them is blank, 0, or false. (0–20 items) |
steps[].ignore_send_window | boolean | nee | Send as soon as it is due, outside the workspace's sending hours too. The per-person limits still apply. |
{
"name": "create_automation",
"arguments": {
"key": "checkout-recovery",
"name": "Checkout recovery",
"audience_label": "Started checkout and left",
"goal_label": "paid",
"from_name": "Acme",
"from_address": "hello@example.com",
"entry": {
"type": "event",
"event": "checkout_started"
},
"exit_rules": {
"goal_event": "payment_completed"
},
"steps": [
{
"offset_seconds": 3600,
"subject": "Still thinking it over, {{ first_name | there }}?",
"html": "<p>Your cart is waiting.</p>"
}
]
}
}update_automationEdit an automation
Automations: Change an automation's name, labels, entry, exit rules, sender, or priority. settings are merged; entry and exit_rules replace the current ones. The key and the status cannot be changed here (use set_automation_status), and emails are changed with set_automation_step. If the automation is on, the change applies to people in it now, and an edit that would leave it unable to send is refused with 422 automation_not_ready. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
name | string | nee | Name shown in the dashboard. (max 200 chars) |
audience_label | string | nee | Who this is for, in plain words, e.g. Started checkout and left. (max 200 chars) |
goal_label | string | nee | What converting means, in a word or two, e.g. paid. (max 80 chars) |
entry | object | nee | How people enter. {type: "event", event} starts on an event recorded with track_event; {type: "manual"} only through enroll_contact. bucket (with segment_id) and date_field (with field) are stored, but nobody enters through them automatically yet. reentry: never (default) or after_end. |
entry.type | string | ja | Entry type. (one of event, bucket, date_field, manual) |
entry.event | string | nee | Event name for an event entry, e.g. checkout_started. |
entry.segment_id | string | nee | Segment ID (seg_…) for a bucket entry. (max 128 chars) |
entry.field | string | nee | Contact field key for a date_field entry. (max 40 chars) |
entry.reentry | string | nee | Whether someone who finished may enter again. (one of never, after_end) |
exit_rules | object | nee | When people leave. goal_event ends the enrolment as converted and credits the latest email sent within attribution_days before it. Each of stop_events ends it without a conversion. An automation with no goal must say so with no_goal: true. Sent whole: it replaces the current rules. |
exit_rules.goal_event | string,null | nee | Event that counts as converting, e.g. payment_completed. |
exit_rules.no_goal | boolean | nee | True when this automation deliberately has no goal. |
exit_rules.stop_events | string[] | nee | Events that take a person out, e.g. ["account_closed"]. (0–20 items) |
exit_rules.attribution_days | integer | nee | Days before the goal within which an email earns the conversion. Default 14. (1–90) |
settings | object | nee | Per-automation settings. Omitted keys keep their value. |
settings.exempt_from_hold | boolean | nee | Skip the workspace's per-person limits (max_emails and min_gap_hours) for this automation. The sending hours still apply, and its emails still count toward the limits of other automations. |
settings.daily_send_cap | integer,null | nee | At most this many emails a day from this automation, counted by the day of the workspace's default_timezone; emails over it wait until the next day. null for no cap. (1–…) |
settings.daily_entry_cap | integer,null | nee | Stored for bucket entries, which are not started automatically yet. It does not limit people entering by event or through enroll_contact. null for no cap. (1–…) |
settings.holdout_pct | number | nee | Percent of people who enter but are sent nothing, to measure what the emails change (0-100). (0–100) |
settings.stale_days | integer | nee | An email more than this many days overdue is skipped instead of sent late. Default 4. (1–365) |
settings.resume_after_days | integer | nee | How long a waiting enrolment waits after the automation ahead of it ends. Default 3. (0–365) |
position | integer | nee | Priority. While one person is in several automations that are on, only the one with the lowest position emails them; the others wait and resume resume_after_days after it ends. (0–100000) |
from_name | string | nee | Sender display name, e.g. Acme. (max 120 chars) |
from_address | string | nee | Sender address on a verified workspace domain (see list_sending_identities). (max 320 chars) |
reply_to | string | nee | Reply-To address. (max 320 chars) |
{
"name": "update_automation",
"arguments": {
"automation_key": "checkout-recovery",
"name": "Checkout recovery",
"settings": {
"holdout_pct": 10
}
}
}delete_automationDelete an automation
DESTRUCTIVE: permanently delete an automation with its emails, language versions, enrolments, send records, and statistics. Only a draft or switched-off automation that nobody is currently in can be deleted; otherwise it fails with 409. Confirm with the user first. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
{
"name": "delete_automation",
"arguments": {
"automation_key": "checkout-recovery"
}
}set_automation_stepCreate or change an email of an automation
Automations: Create the email at position, or change the fields you pass on the one that is there; fields left out keep their value. If the automation is on, people who have not received this email yet get the new version, so confirm the wording with the user. An existing email keeps its ID: people who already received it are not sent it again. With template, the email becomes that template of the library (see list_automation_templates): its subject, preview text and content replace the email's and its language versions are removed. While the automation is on, an email must keep a subject and content, and may not hold a placeholder of the template library such as [First step] or print a workspace name that is blank (422 automation_not_ready with problems). Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
position | integer | ja | Position of the email in the automation, 1 to 50. (1–50) |
template | string | nee | Id of a template of the library, e.g. welcome-note (not a set). The email becomes that template; other fields passed here are applied on top. The email's wait is not the template's: pass offset_seconds. (max 63 chars) |
subject | string | nee | Subject line. Merge tags such as {{ first_name | there }} are filled per contact. (max 998 chars) |
preheader | string | nee | Inbox preview line. (max 300 chars) |
content | object | nee | Block document ({type: "doc", content: [...]}), as the dashboard editor stores it. Sent without html, it is rendered with the workspace design. On an email built in the dashboard's drag-and-drop builder (editor design) it is the builder's project instead: opaque, never write one by hand, and send it back only unchanged together with its html. |
html | string | nee | HTML body. The unsubscribe footer is added automatically. |
text | string | nee | Berichttekst in plaintext. |
editor | string | nee | How the email is made: blocks (the dashboard's writing editor, the default), html (your own HTML) or design (the dashboard's drag-and-drop builder). Only the builder makes a design; to send a designed email yourself, send html with editor html. (one of blocks, html, design) |
offset_seconds | integer | nee | When the email is due, in seconds after the moment the person entered (3600 = one hour, 86400 = one day). May be negative for emails that lead up to a date. When several emails are due at once, only the latest is sent and the earlier ones are skipped. (-31622400–31622400) |
skip_if_empty | string[] | nee | Merge keys, e.g. ["fields.plan"]. The email is skipped for a contact where any of them is blank, 0, or false. (0–20 items) |
ignore_send_window | boolean | nee | Send as soon as it is due, outside the workspace's sending hours too. The per-person limits still apply. |
{
"name": "set_automation_step",
"arguments": {
"automation_key": "checkout-recovery",
"position": 2,
"offset_seconds": 86400,
"subject": "Your cart is still here",
"html": "<p>Pick up where you left off.</p>"
}
}delete_automation_stepRemove an email from an automation
DESTRUCTIVE: remove the email at position from an automation. It is no longer sent or listed; records of who already received it are kept. While the automation is on, its only email cannot be removed (409). Confirm with the user first. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
position | integer | ja | Position of the email in the automation, 1 to 50. (1–50) |
{
"name": "delete_automation_step",
"arguments": {
"automation_key": "checkout-recovery",
"position": 3
}
}set_automation_step_variantCreate or change a language version of an email
Automations: Save the version of one email for contacts whose locale is this language tag (e.g. fr); a contact with a regional locale such as pt-br gets the pt version when there is no pt-br one. Fields left out keep their value. A version without a body uses the email's own body, and a blank subject or preheader falls back to the email's. Contacts without a matching version get the email as written. If the automation is on, matching contacts who have not received this email yet get this version. While the automation is on, a version may not hold a placeholder of the template library or print a workspace name that is blank (422 automation_not_ready). Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
position | integer | ja | Position of the email in the automation, 1 to 50. (1–50) |
locale | string | ja | Language tag of the version, e.g. fr or pt-br. (max 35 chars) |
subject | string | nee | Subject line. Merge tags such as {{ first_name | there }} are filled per contact. (max 998 chars) |
preheader | string | nee | Inbox preview line. (max 300 chars) |
content | object | nee | Block document ({type: "doc", content: [...]}), as the dashboard editor stores it. Sent without html, it is rendered with the workspace design. On an email built in the dashboard's drag-and-drop builder (editor design) it is the builder's project instead: opaque, never write one by hand, and send it back only unchanged together with its html. |
html | string | nee | HTML body. The unsubscribe footer is added automatically. |
text | string | nee | Berichttekst in plaintext. |
{
"name": "set_automation_step_variant",
"arguments": {
"automation_key": "checkout-recovery",
"position": 1,
"locale": "fr",
"subject": "Vous hésitez encore ?",
"html": "<p>Votre panier vous attend.</p>"
}
}set_automation_statusTurn an automation on or off
SENDS REAL EMAIL when status is on: from then on, everyone who enters the automation is emailed on its schedule, within the workspace's sending limits and hours (get_sending_limits), and people already in it continue. Use preview_automation to see who would get which email. Only turn it on when the user asked for this automation to start. Turning on checks an entry, a goal or exit_rules.no_goal, at least one email with a subject and content, no placeholder of the template library such as [First step] or [Link to plans] left in any email (subject, preview text, body, or a link's address), and no blank workspace name that an email prints (422 automation_not_ready with problems, which names each email and detail; get_automation lists the same under to_fill), a sender on a verified domain (403), and an active subscription (402). off stops new entries and sending; people in it stay and continue if it is turned on again, except that an email more than stale_days overdue by then is skipped. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
status | string | ja | on to start sending, off to stop. (one of on, off) |
{
"name": "set_automation_status",
"arguments": {
"automation_key": "checkout-recovery",
"status": "off"
}
}send_automation_test_emailSend one automation email to yourself as a test
SENDS REAL EMAIL: one email of an automation, marked [Test], to the account's own address (get_account -> user.email) and nowhere else; a recipient cannot be given. It is the email as the automation would send it (the language version for locale, the same sender, unsubscribe footer and checks), with stand-in values for its merge tags; sample replaces any of them. A test is not part of the automation: nobody is enrolled, it is in no report, it counts toward nobody's per-person sending limits, it is not tracked, and the automation does not have to be on. It counts toward the workspace's own sending allowance. With dry_run: true nothing is sent and the result is the email as the test would deliver it, with locales and the sample values used. Fails with 422 automation_not_ready when the automation has no sender or the email has no subject or content, and 429 test_limit_reached after 100 test emails in 24 hours. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
position | integer | ja | Position of the email in the automation, 1 to 50. (1–50) |
locale | string | nee | Send the language version a contact with this language would get (such as fr or pt-br). Omit for the email as written. (max 35 chars) |
sample | object | nee | Values to print for merge tags, by key, in place of the stand-ins (first_name is Alex, and so on). email, product_name, and sender_name cannot be set. |
dry_run | boolean | nee | Send nothing; return the email as the test would deliver it. |
{
"name": "send_automation_test_email",
"arguments": {
"automation_key": "checkout-recovery",
"position": 1
}
}send_automation_testSend every email of an automation to yourself as tests
SENDS REAL EMAIL: every email of an automation, in order, marked [Test 1 of 3], [Test 2 of 3] and so on, to the account's own address (get_account -> user.email) and nowhere else, without waiting for the emails' delays. Rendering, footer, checks and stand-in values are as in send_automation_test_email. A test is not part of the automation: nobody is enrolled, it is in no report, it counts toward nobody's per-person sending limits, it is not tracked, and the automation does not have to be on. It counts toward the workspace's own sending allowance. Nothing is sent unless everything can be: a sender, a subject and content on every email (422 automation_not_ready with problems), and room for all of them under 100 test emails in 24 hours (429 test_limit_reached). If a send is refused after others went out, the rest are not tried and each email's outcome is returned. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
locale | string | nee | Send the language version a contact with this language would get (such as fr or pt-br). Omit for the email as written. (max 35 chars) |
sample | object | nee | Values to print for merge tags, by key, in place of the stand-ins (first_name is Alex, and so on). email, product_name, and sender_name cannot be set. |
{
"name": "send_automation_test",
"arguments": {
"automation_key": "checkout-recovery"
}
}enroll_contactAdd a contact to an automation
SENDS REAL EMAIL on the automation's schedule: starts the automation for one existing, subscribed contact, counting from anchor_at (now by default). Only call it when the user asked for this person to get this sequence. The automation must be on (409 automation_not_on). Fails with 404 when the email is not a contact (add it with upsert_contact), 422 when the contact cannot be mailed, and 409 when the contact is already in it or went through it before and re-entry is not allowed. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
email | string | ja | Email address of an existing contact. (max 320 chars) |
properties | object | nee | Up to 50 values (string, number, or boolean; strings are cut at 500 characters), e.g. {"plan": "pro"}. Usable in the automation's emails as merge tags such as {{ plan }}. The names email, name, first_name, last_name, and fields are reserved. |
anchor_at | string | nee | The moment the emails' offsets count from, ISO 8601 with a time zone. Defaults to now; may lie ahead for emails that lead up to a date. (max 40 chars) |
{
"name": "enroll_contact",
"arguments": {
"automation_key": "checkout-recovery",
"email": "ada@example.net",
"properties": {
"plan": "pro"
}
}
}exit_contactTake a contact out of an automation
Automations: End a contact's open enrolment in one automation, so no further emails of it are sent to them. Other automations and broadcasts are not affected, and the contact stays subscribed. Fails with 404 when the contact is not in it. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
email | string | ja | Email address of the contact. (max 320 chars) |
reason | string | nee | Why, for the record (max 200 chars). Defaults to manual. (max 200 chars) |
{
"name": "exit_contact",
"arguments": {
"automation_key": "checkout-recovery",
"email": "ada@example.net",
"reason": "Asked support to stop"
}
}preview_automationPreview what an automation would send now
Automations: A dry run. For the people in the automation now, in the order they come due, what would happen if each were evaluated at this moment. outcome is send (the email in step would go out), scheduled (nothing is due before until), held (the email waits until until; reason is limit_cap, limit_gap, window, or daily_cap), waiting (behind the higher-priority automation in behind), skip (reason is stale, empty_field, or holdout), exit (the contact can no longer be mailed and would leave), complete, blocked (automation_off or subscription_required), or in_progress. Read-only: nothing is sent or changed. Use it before set_automation_status, or after changing limits, to see who gets which email. It applies the automation's own rules and does not foresee a refusal only a real send meets, such as the workspace's daily sending limit or a paused sender. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "preview_automation",
"arguments": {
"automation_key": "checkout-recovery"
}
}get_automations_overviewGet results across all automations
Automations: What every automation of the workspace did in a date range (the last 30 days by default, at most 366 days): totals and one entry per day for people who entered, emails sent, delivered, opened, clicked, and converted (a goal event credited to an email), plus bounces, complaints, unsubscribes, and held (emails made to wait by a limit). Days on which nothing happened are in the series with zeros. domain narrows it to the automations that send from one domain (none: those with no sender yet). Opens and clicks are estimates: each email counts once, at its first open or click by a person, and automated requests (scanners, link previews, privacy prefetching) are never counted. Never claim that a person read an email. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
from | string | nee | First day of the report as a UTC date (YYYY-MM-DD), inclusive. |
to | string | nee | Last day of the report as a UTC date (YYYY-MM-DD), inclusive. |
domain | string | nee | Only the automations that send from this domain: the exact domain of their from_address (e.g. example.com), or none for automations with no sender yet. (max 253 chars) |
{
"name": "get_automations_overview",
"arguments": {
"from": "2026-10-20",
"to": "2026-11-18"
}
}get_automation_reportGet the results of one automation
Automations: The results of one automation in a date range (the last 30 days by default, at most 366 days): the same totals and daily series as get_automations_overview, and steps, one row per email with what it sent and what came of it. An email that was removed is listed with archived: true while it still has numbers in the range. Opens and clicks are estimates: each email counts once, at its first open or click by a person, and automated requests (scanners, link previews, privacy prefetching) are never counted. Never claim that a person read an email. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
from | string | nee | First day of the report as a UTC date (YYYY-MM-DD), inclusive. |
to | string | nee | Last day of the report as a UTC date (YYYY-MM-DD), inclusive. |
{
"name": "get_automation_report",
"arguments": {
"automation_key": "checkout-recovery"
}
}list_automation_peopleList the people in an automation
Automations: One row per person who did did in an automation, most recent first: entered (the default: everyone who was ever in it), sent, delivered, opened, clicked, converted (their goal was credited to an email), bounced, unsubscribed, or waiting (waiting now behind a higher-priority automation). step narrows every filter except entered and waiting to one email. Each row has the contact's email and name, when they did it, their enrolment's status, and latest: the most recent thing that happened to them in the automation. counts says how many people each filter would list. Read one person's full history with get_automation_person. Opens and clicks are estimates: each email counts once, at its first open or click by a person, and automated requests (scanners, link previews, privacy prefetching) are never counted. Never claim that a person read an email. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
did | string | nee | What the people did. Defaults to entered. (one of entered, sent, delivered, opened, clicked, converted, bounced, unsubscribed, waiting) |
step | integer | nee | Only this email of the automation, by its position. (1–50) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_automation_people",
"arguments": {
"automation_key": "checkout-recovery",
"did": "clicked"
}
}get_automation_personGet one person's history in an automation
Automations: Everything that happened to one contact in an automation: each enrolment and how it ended, each email with when it was sent, delivered, first opened, first clicked, bounced, complained about, or unsubscribed from, every open and click on it (machine: true marks an automated request, which is not counted), and the conversion with the email it was credited to. Fails with 404 for a contact that was never in the automation. Opens and clicks are estimates: each email counts once, at its first open or click by a person, and automated requests (scanners, link previews, privacy prefetching) are never counted. Never claim that a person read an email. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
automation_key | string | ja | Automation key, as returned by list_automations (e.g. checkout-recovery). (max 63 chars) |
contact_id | string | ja | Contact ID (starts with ct_) or the contact's email address. (max 320 chars) |
{
"name": "get_automation_person",
"arguments": {
"automation_key": "checkout-recovery",
"contact_id": "ct_123"
}
}get_sending_limitsGet automation sending limits
Automations: How much automation email one person may get across every automation, and when: at most max_emails in any period_days, at least min_gap_hours apart, only between window_start and window_end (hours in the contact's time zone, or default_timezone) on weekdays (0 = Sunday to 6 = Saturday). An email that would break a limit is not dropped: it waits until the limits allow it. Also product_name and sender_name, available to every automation email as merge tags. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
Geen parameters.
{
"name": "get_sending_limits",
"arguments": {}
}update_sending_limitsUpdate automation sending limits
Automations: Change the workspace's per-person limits and sending hours for automation email. Omitted keys keep their value. Looser limits mean people can get more email, sooner: confirm with the user before raising max_emails, shortening min_gap_hours, or widening the hours. product_name and sender_name are the names the emails of the template library print; one that an automation that is on prints cannot be cleared (409 workspace_name_in_use). Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
max_emails | integer | nee | Most automation emails one person may get in period_days. Default 2. (1–50) |
period_days | integer | nee | The period max_emails applies to, in days. Default 7. (1–90) |
min_gap_hours | integer | nee | Least time between two automation emails to one person, in hours. Default 44. (0–720) |
window_start | integer | nee | First hour of the day emails may go out, local time (0-23). Default 9. (0–23) |
window_end | integer | nee | Hour sending stops, local time (1-24); must be later than window_start. Default 18. (1–24) |
weekdays | integer[] | nee | Days emails may go out: 0 = Sunday to 6 = Saturday. Default [1, 2, 3, 4, 5]. (1–7 items) |
default_timezone | string | nee | IANA time zone used for contacts that have none, e.g. Europe/London. (max 64 chars) |
product_name | string | nee | Your product's name, for {{ product_name }}. (max 120 chars) |
sender_name | string | nee | Who the emails are from, for {{ sender_name }}. (max 120 chars) |
{
"name": "update_sending_limits",
"arguments": {
"max_emails": 3,
"min_gap_hours": 24,
"default_timezone": "Europe/London"
}
}list_automation_templatesList automation templates
Automations: The template library: ready-made lifecycle emails to start an automation from instead of writing one. It covers welcome, onboarding tips, a nudge to finish setup (activation), trial ending and trial ended, abandoned checkout, failed payment (dunning), receipt, upgrade at a usage limit, feature announcement, review request, feedback score (NPS), cancellation survey, and winback for retention. Each template has a name, a one-line purpose, the goal it serves (group), its subject, the merge tags it prints, and start: the suggested entry event, the email's wait, and the goal event that ends the automation for a person. sets are templates that arrive together as one automation: three onboarding tips, trial ending then trial ended, and payment failed then a last notice. fill_in lists what only the user knows: placeholders in square brackets such as [First step] or [Link to plans], and the workspace names the email prints. Email bodies are not included; use get_automation_template. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_automation_templates",
"arguments": {}
}get_automation_templateGet an automation template
Automations: One template or one set of the template library, as the draft automation it would make: the suggested start and goal, what the user must fill in, and every email in order with its wait, subject, the email as a block document (content), and preview: the subject and text as this workspace would send them, with sample values for the merge tags. Read it to show the user a welcome, onboarding, trial, abandoned checkout, failed payment (dunning), upgrade, cancellation or winback email before using it. Placeholders such as [First step] are shown as written; a workspace name that is not set reads "Your product" or "Your name" in the preview. Then use_automation_template makes the draft, or set_automation_step with template loads one email into an existing automation. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Id of a template or a set, as returned by list_automation_templates (e.g. welcome-note, checkout-not-finished, payment-failed-notices). (max 63 chars) |
{
"name": "get_automation_template",
"arguments": {
"template_id": "welcome-note"
}
}use_automation_templateCreate an automation from a template
Automations: Create a draft automation from a template or a set of the library, ready-made: a welcome email, three onboarding tips, a nudge to finish setup, trial ending and trial ended, abandoned checkout, failed payment (dunning) notices, a receipt, an upgrade email at a usage limit, a feature announcement, a review request, a feedback score, a cancellation survey, or a winback for retention. The draft has the emails, the suggested entry event and the suggested goal. Nothing is sent: it stays a draft until set_automation_status turns it on, and that is refused while anything in to_fill is left. to_fill lists each placeholder to replace, by email (ask the user for the real words and links, then use set_automation_step), and each workspace name the emails print that is blank (product_name, sender_name: set with update_sending_limits). Make sure the entry event is one the workspace records (list_event_names); change the start with update_automation. from_address must be on a verified domain. Fails with 404 for an unknown template and 409 when key is taken. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
template_id | string | ja | Id of a template or a set, as returned by list_automation_templates (e.g. welcome-note, checkout-not-finished, payment-failed-notices). (max 63 chars) |
key | string | nee | Address of the new automation: 1-63 characters of a-z, 0-9, and -. Defaults to the template's id, with a number added when that is taken. (max 63 chars) |
name | string | nee | Name shown in the dashboard. Defaults to the template's own name. (max 200 chars) |
from_name | string | nee | Sender display name, e.g. Acme. (max 120 chars) |
from_address | string | nee | Sender address on a verified workspace domain (see list_sending_identities). (max 320 chars) |
reply_to | string | nee | Reply-To address. (max 320 chars) |
{
"name": "use_automation_template",
"arguments": {
"template_id": "welcome-note",
"name": "Welcome",
"from_name": "Dana from Acme",
"from_address": "dana@example.com"
}
}list_eventsList what contacts did
Automations: The events recorded for the workspace, newest first: who (the contact's id, email, and name), what they did (the event name, and the same as words), when, its properties, where it came from (source.type: api for the workspace's own code, connection with the connection's name, upload for a spreadsheet, system for SendHQ itself), and effects: the automations it started, ended, or converted for that contact. Filter by contact (a contact ID or an email address), name (one event name), and from / to. With contact, the result also lists every automation that contact is or was in (enrollments). An event being recorded does not mean an email was sent: check the automation with list_automation_people. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
contact | string | nee | Only this contact: a contact ID or an email address. (max 320 chars) |
name | string | nee | Only this event, e.g. checkout_started. See list_event_names. (max 64 chars) |
from | string | nee | Events from this UTC date (YYYY-MM-DD) or ISO 8601 date-time on. (max 40 chars) |
to | string | nee | Events up to this UTC date (the whole day) or ISO 8601 date-time. (max 40 chars) |
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_events",
"arguments": {
"name": "checkout_started",
"from": "2026-11-01"
}
}list_event_namesList the kinds of event recorded
Automations: Every distinct event name recorded in the last 30 days with how many times, the most frequent first, each with the name as words (checkout_started reads checkout started). Use it to see what the workspace is being told about before creating an automation that starts on an event. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_event_names",
"arguments": {}
}list_connectionsList connections
Automations: The workspace's connections. A connection is a secret address another system posts to, such as a payment provider's webhook; what arrives is recorded as events, exactly as track_event records them. Each has its kind (stripe, dodo, or generic), whether it is enabled, whether a signing secret is set, the last four characters of its address, and last_delivery in plain words such as "Recorded 2 events" or "Refused: bad signature". The address and the signing secret are never returned here. Paginated. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_connections",
"arguments": {}
}get_connectionGet a connection and its last deliveries
Automations: One connection with its last 50 deliveries, newest first: when each arrived, whether it was recorded, skipped, or refused and why (text says it in plain words), the sender's own event type, the names of the events recorded, and the contact's email address. Payloads are not stored. Use it to find out why something a provider sent did not show up. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
connection_id | string | ja | Connection ID, as returned by list_connections (e.g. acn_…). (max 128 chars) |
{
"name": "get_connection",
"arguments": {
"connection_id": "acn_123"
}
}create_connectionCreate a connection
SENDS REAL EMAIL later, when an automation is listening: from the moment the address this returns is given to another system, everything that system posts is recorded as events without anyone looking, and a recorded event starts every automation that is on and starts on it. Only create one when the user asked to connect that system. Returns address once; it cannot be read again, so hand it to the user at once. kind is stripe or dodo (mapped for you: checkout_completed, checkout_abandoned, paid, payment_failed, subscription_started, subscription_renewed, subscription_cancelled, plan_changed) or generic with a mapping. consent_basis is recorded on every contact the connection creates. The provider's signing secret is set by a person in the dashboard or with the REST API, not here. A workspace may have 10 connections (409 connection_limit_reached). Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
name | string | ja | What to call it, e.g. Stripe. (max 80 chars) |
kind | string | ja | stripe, dodo, or generic. (one of generic, stripe, dodo) |
consent_basis | string | ja | How the people this connection tells you about agreed to receive your email, e.g. Bought a plan on acme.com and accepted product emails. Recorded on every contact it creates. 10-500 characters. (max 500 chars) |
event_prefix | string | nee | Put in front of every event name, e.g. stripe_. (max 32 chars) |
enabled | boolean | nee | Defaults to true. Pass false to create it switched off. |
mapping | object | nee | For a generic connection: dotted paths into the payload it posts, such as customer.email. email is required, and either event or event_name. |
mapping.email | string | nee | Where the contact's email address is. (max 120 chars) |
mapping.event | string | nee | Where the payload names what happened. Order Placed becomes the event order_placed. (max 120 chars) |
mapping.event_name | string | nee | One fixed event name, instead of event. (max 64 chars) |
mapping.time | string | nee | Where the time it happened is (ISO 8601, or Unix seconds or milliseconds). Defaults to the time of arrival. (max 120 chars) |
mapping.id | string | nee | Where a unique ID of the message is, so a retried delivery is recorded once. (max 120 chars) |
mapping.keep | string[] | nee | The fields to keep as event properties. Defaults to the top-level text, number, and boolean fields. (0–50 items) |
{
"name": "create_connection",
"arguments": {
"name": "Stripe",
"kind": "stripe",
"consent_basis": "Bought a plan on acme.com and accepted product emails"
}
}update_connectionChange a connection or switch it on or off
SENDS REAL EMAIL later when enabled is set to true: what the connected system posts is recorded as events again, and a recorded event starts every automation that is on and starts on it. Only switch one on when the user asked. Also changes name, consent_basis, event_prefix, or a generic connection's mapping. While enabled is false the address answers 404 and records nothing. The kind cannot be changed. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
connection_id | string | ja | Connection ID, as returned by list_connections (e.g. acn_…). (max 128 chars) |
name | string | nee | A new name. (max 80 chars) |
enabled | boolean | nee | true: record what arrives. false: answer 404 and record nothing. |
consent_basis | string | nee | How the people this connection tells you about agreed to receive your email, e.g. Bought a plan on acme.com and accepted product emails. Recorded on every contact it creates. 10-500 characters. (max 500 chars) |
event_prefix | string | nee | Put in front of every event name, e.g. stripe_. (max 32 chars) |
mapping | object | nee | For a generic connection: dotted paths into the payload it posts, such as customer.email. email is required, and either event or event_name. |
mapping.email | string | nee | Where the contact's email address is. (max 120 chars) |
mapping.event | string | nee | Where the payload names what happened. Order Placed becomes the event order_placed. (max 120 chars) |
mapping.event_name | string | nee | One fixed event name, instead of event. (max 64 chars) |
mapping.time | string | nee | Where the time it happened is (ISO 8601, or Unix seconds or milliseconds). Defaults to the time of arrival. (max 120 chars) |
mapping.id | string | nee | Where a unique ID of the message is, so a retried delivery is recorded once. (max 120 chars) |
mapping.keep | string[] | nee | The fields to keep as event properties. Defaults to the top-level text, number, and boolean fields. (0–50 items) |
{
"name": "update_connection",
"arguments": {
"connection_id": "acn_123",
"enabled": false
}
}delete_connectionDelete a connection
DESTRUCTIVE: permanently delete a connection with its delivery records. Its address stops working at once, so the system that posts to it starts getting 404 and nothing more is recorded from it. The events it already recorded stay. Confirm with the user first; to pause one instead, use update_connection with enabled: false. Automations are enabled workspace by workspace: a workspace that is not enabled gets 403 automations_not_enabled.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
connection_id | string | ja | Connection ID, as returned by list_connections (e.g. acn_…). (max 128 chars) |
{
"name": "delete_connection",
"arguments": {
"connection_id": "acn_123"
}
}Account, gebruik, analytics en sleutels
get_accountAccount, gebruik en facturering ophalen
E-mailadres van de accounteigenaar, abonnement/toegangsniveau, gebruikte afleveringen aan ontvangers in de huidige periode vs. quotum, gebruikte domeinen vs. limiet, bijlagenverkeer, reputatieoverzicht, abonnementsstatus, gepubliceerde abonnementen en aantallen in de workspace. Gebruik dit om het resterende quotum te controleren of om te zien naar wie de proefperiode kan afleveren (het e-mailadres van het account).
Geen parameters.
{
"name": "get_account",
"arguments": {}
}get_account_diagnosticsDiagnose sending and receiving
One read that explains what is wrong with sending or receiving in this workspace: an issues list (unverified domains and missing DKIM records, inbound MX not ready, paused or throttled senders, quota or daily limit reached, trial restrictions, high bounce or complaint rates, failing webhooks), plan and usage against limits, each domain with its DKIM and inbound state, sending identities, 30-day deliverability and sender reputation, suppressions and unsubscribes, and the last 30 days of messages that were not sent (with reasons) plus bounce, complaint and reject events. Start here when a user asks why mail is not arriving. Never returns message bodies or secrets.
Geen parameters.
{
"name": "get_account_diagnostics",
"arguments": {}
}get_analyticsVerzendanalytics ophalen
Dashboardanalytics over de laatste 7, 30 of 90 dagen: totalen voor sent/received/delivered/bounced/blocked/opened/clicked/complaint, een dagelijkse tijdlijn, de belangrijkste verzenddomeinen en de meest gebruikte onderwerpen.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
days | integer | nee | Venster in dagen: 7, 30 (standaard) of 90. (een van 7, 30, 90) |
{
"name": "get_analytics",
"arguments": {
"days": 30
}
}list_api_keysMetadata van API-sleutels opvragen
Vraagt namen, niet-geheime prefixen en het tijdstip van laatste gebruik van API-sleutels op. Alleen-lezen: deze MCP-server kan geen sleutels aanmaken, roteren of intrekken; dat doet een mens in het dashboard. Gepagineerd: het resultaat bevat pagination {offset, limit, returned, total?, has_more, next_offset}.
| Parameter | Type | Verplicht | Beschrijving |
|---|---|---|---|
limit | integer | nee | Paginagrootte. Standaard 50. (standaard 50; 1–200) |
offset | integer | nee | Aantal records dat wordt overgeslagen. Gebruik pagination.next_offset van de vorige pagina. (standaard 0; 0–…) |
{
"name": "list_api_keys",
"arguments": {}
}get_service_healthStatus van de SendHQ-dienst controleren
Controleert of de SendHQ API bereikbaar is en welke mailprovider actief is. Heeft geen geldige API-sleutel nodig.
Geen parameters.
{
"name": "get_service_health",
"arguments": {}
}Overzicht van de API-dekking
Elke bewerking in de publieke API en de tool die haar dekt. Alles wat een gebruiker in het dashboard kan doen en een API heeft, wordt gedekt; de uitzonderingen hieronder zijn bewust.
| Endpoint | Tool | Opmerkingen |
|---|---|---|
| POST /emails | send_email | Eén e-mail verzenden |
| POST /emails/batch | send_batch | Maximaal 100 individuele berichten verzenden |
| GET /emails | list_emails | Verzonden en ontvangen e-mail opvragen |
| GET /emails/:id | get_email | Een e-mail en de bijlagen ophalen |
| PATCH /emails/:id | mark_email | Leesstatus, archivering, spam, categorie of belangrijkheid bijwerken |
| POST /emails/:id/labels | label_email | Labels aan een e-mail toevoegen of ervan verwijderen |
| DELETE /emails/:id | delete_email | Een bewaarde e-mail verwijderen |
| GET /emails/:id/events | list_email_events | Bezorgevents van een e-mail opvragen |
| GET /threads/:id | get_thread | Een conversatie in chronologische volgorde ophalen |
| GET /labels | list_labels | Labels opvragen met aantallen berichten en sorteerregels |
| POST /labels | create_label | Een label aanmaken, optioneel met automatische sorteerregels |
| GET /labels/:id | get_label | Een label ophalen op ID of naam |
| PATCH /labels/:id | update_label | Een label hernoemen, een andere kleur geven of er een bucket van maken |
| DELETE /labels/:id | delete_label | Een label verwijderen zonder de e-mail erin te verwijderen |
| POST /labels/:id/rules | create_label_rule | Een automatische sorteerregel aan een label toevoegen |
| DELETE /labels/:id/rules/:rule_id | delete_label_rule | Een automatische sorteerregel verwijderen |
| POST /drafts | create_draft | Een concept in de editor aanmaken |
| GET /drafts | list_drafts | Concepten uit de editor opvragen |
| GET /drafts/:id | get_draft | Een concept en de bijlagen ophalen |
| PUT /drafts/:id | update_draft | Inhoud van een concept vervangen |
| DELETE /drafts/:id | delete_draft | Een concept weggooien |
| POST /drafts/:id/attachments | upload_attachment | Een bijlage uploaden naar een concept |
| GET /attachments/:id | download_attachment | Een privébijlage downloaden |
| DELETE /attachments/:id | delete_attachment | Een privébijlage verwijderen |
| GET /sending-identities | list_sending_identities | Geverifieerde afzenderidentiteiten opvragen |
| GET /templates | list_templates | Gehoste templates opvragen |
| POST /templates | create_template | Een gehoste template aanmaken |
| GET /templates/:id | get_template | Concepten, releases en gebruik ophalen |
| PUT /templates/:id/draft | update_template_draft | Een templateconcept automatisch opslaan |
| POST /templates/:id/draft | create_template_draft | Een nieuw concept maken op basis van de gepubliceerde release |
| POST /templates/:id/render | render_template | De exacte serveruitvoer renderen |
| POST /templates/:id/test | send_template_test | Een testsnapshot verzenden |
| POST /templates/:id/publish | publish_template | Een onveranderlijke templaterelease publiceren |
| POST /templates/:id/archive | archive_template | Een template archiveren |
| POST /templates/:id/restore | restore_template | Een gearchiveerde template herstellen |
| POST /domains | add_domain | Een verzenddomein toevoegen |
| GET /domains | list_domains | Domeinen en gecachte DNS-status opvragen |
| GET /domains/:id | get_domain | Configuratiegegevens van een domein ophalen |
| POST /domains/:id/verify | verify_domain | Refresh domain and DNS verification |
| POST /domains/:id/inbound/setup | setup_inbound | Provision inbound receiving |
| POST /domains/:id/inbound/verify | verify_inbound | Inkomende MX-routering verifiëren |
| DELETE /domains/:id | delete_domain | Een domein verwijderen |
| GET /dns/provider | get_dns_provider | De gezaghebbende DNS-provider en relatieve recordhosts detecteren |
| GET /dns/domain-connect/connect | get_domain_connect_link | Een Domain Connect-toestemmingslink maken voor DNS-configuratie met één klik |
| POST /inboxes | create_inbox | Een inkomend adres aanmaken |
| GET /inboxes | list_inboxes | Inkomende adressen opvragen |
| GET /inboxes/:id | get_inbox | Een inkomend adres ophalen |
| PATCH /inboxes/:id | update_inbox | Een inbox hernoemen, inschakelen of uitschakelen |
| PUT /inboxes/:id/forwarding | set_inbox_forwarding | De ontvangen e-mail van een inbox doorsturen naar een ander adres |
| DELETE /inboxes/:id | delete_inbox | Een inbox verwijderen en de berichten bewaren |
| GET /deliverability/stats | deliverability_stats | Bezorgstatistieken over 30 dagen ophalen |
| GET /deliverability/reputation | list_sender_reputation | Reputatiestatus per exacte afzenderidentiteit opvragen |
| GET /deliverability/account | deliverability_account | Account delivery rates, daily ladder, and bounce trend |
| GET /deliverability/domains | deliverability_domains | Per-domain sent, delivered, hard and soft bounces, complaints, and failures |
| GET /deliverability/senders | deliverability_senders | Per-From-address delivery rates |
| POST /deliverability/score | score_email | Score an email's content before it is sent |
| GET /emails/:id/delivery | email_delivery | Delivery timeline for one email, with bounce and complaint reasons |
| GET /threads/:id/delivery | thread_delivery | Per-thread delivery counts and per-message failure reasons |
| GET /suppressions | list_suppressions | Suppressies van de workspace opvragen |
| DELETE /suppressions/:email | remove_suppression | Een bouncesuppressie verwijderen die daarvoor in aanmerking komt |
| GET /blocked-recipients | list_blocked_recipients | Bounces, klachten en afmeldingen opvragen |
| GET /webhooks | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| POST /webhooks | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| GET /webhooks/:id | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| PATCH /webhooks/:id | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| DELETE /webhooks/:id | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| POST /webhooks/:id/rotate-secret | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| POST /webhooks/:id/test | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| GET /webhooks/:id/deliveries | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| GET /webhooks/:id/deliveries/:deliveryId | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| POST /webhooks/:id/deliveries/:deliveryId/retry | niet beschikbaar | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| GET /contacts | list_contacts | List contacts |
| POST /contacts | create_contact | Add a contact with its consent basis |
| PUT /contacts | upsert_contact | Create or update a contact by email |
| POST /contacts/bulk | bulk_update_contacts | Tag, move, unsubscribe, or delete many contacts at once |
| GET /contacts/export | niet beschikbaar | Image uploads take a raw binary body and the export returns a CSV file meant for a person to download. Agents reuse uploaded images with list_uploaded_images and read the same contacts, filters, tags, and fields as JSON with list_contacts (paginated). |
| GET /contacts/:id | get_contact | Retrieve a contact by ID or email |
| PATCH /contacts/:id | update_contact | Update a contact's name, fields, or tags, or unsubscribe it |
| DELETE /contacts/:id | delete_contact | Delete a contact and its list memberships |
| POST /contact-imports | import_contacts | Import contacts from CSV |
| GET /contact-imports | list_contact_imports | List recent contact imports |
| GET /tags | list_tags | List contact tags with how many contacts carry each |
| GET /contact-fields | list_contact_fields | List custom contact field definitions |
| PUT /contact-fields/:key | set_contact_field | Define or change a custom contact field |
| DELETE /contact-fields/:key | delete_contact_field | Delete a custom field definition |
| GET /segments | list_segments | List saved segments with live counts |
| POST /segments | create_segment | Save a segment |
| POST /segments/preview | preview_segment | Count and sample the contacts that match unsaved conditions |
| GET /segments/:id | get_segment | Retrieve a segment and its live count |
| PATCH /segments/:id | update_segment | Rename a segment or change its conditions |
| DELETE /segments/:id | delete_segment | Delete a segment |
| GET /lists | list_lists | List contact lists with member counts |
| POST /lists | create_list | Create a list with an optional signup form, welcome email, and newsletter site |
| GET /lists/:id | get_list | Retrieve a list |
| PATCH /lists/:id | update_list | Rename a list or change its signup form, welcome email, or site |
| DELETE /lists/:id | delete_list | Delete a list without deleting its contacts |
| POST /lists/:id/contacts | add_list_contacts | Add existing contacts to a list |
| DELETE /lists/:id/contacts/:contact_id | remove_list_contact | Remove a contact from a list |
| GET /broadcasts | list_broadcasts | List broadcasts |
| POST /broadcasts | create_broadcast | Create a broadcast draft |
| GET /broadcasts/:id | get_broadcast | Retrieve a broadcast and its delivery totals |
| PATCH /broadcasts/:id | update_broadcast | Edit a draft broadcast |
| DELETE /broadcasts/:id | delete_broadcast | Delete a draft broadcast |
| GET /broadcasts/:id/checks | check_broadcast | Run the pre-send checks for a broadcast |
| POST /broadcasts/:id/test | send_broadcast_test | Send a test copy of a draft |
| POST /broadcasts/:id/schedule | schedule_broadcast | Schedule a draft to send later |
| POST /broadcasts/:id/unschedule | unschedule_broadcast | Unschedule a draft |
| POST /broadcasts/:id/duplicate | duplicate_broadcast | Copy a broadcast into a new draft |
| POST /broadcasts/:id/send | send_broadcast | Send a broadcast to its audience |
| POST /broadcasts/:id/send-more | send_broadcast_to_more | Send a sent broadcast to more of its audience |
| POST /broadcasts/:id/cancel | cancel_broadcast | Cancel a draft or sending broadcast |
| GET /broadcasts/:id/recipients | list_broadcast_recipients | List a broadcast's recipients, outcomes, and engagement |
| GET /broadcasts/:id/report | get_broadcast_report | Retrieve a broadcast's engagement report |
| GET /campaigns/overview | get_campaign_overview | Retrieve subscriber growth and recent broadcast performance |
| GET /newsletter-settings | get_newsletter_settings | Retrieve newsletter settings |
| PATCH /newsletter-settings | update_newsletter_settings | Change newsletter settings |
| POST /uploads/images | niet beschikbaar | Image uploads take a raw binary body and the export returns a CSV file meant for a person to download. Agents reuse uploaded images with list_uploaded_images and read the same contacts, filters, tags, and fields as JSON with list_contacts (paginated). |
| GET /uploads/images | list_uploaded_images | List recently uploaded images |
| POST /events | track_event | Record something a contact did |
| POST /events/batch | niet beschikbaar | History import is a one-time migration step for the account owner and requires a dashboard session. Bulk events are for server-side backfills through the REST API; an agent records what one person did with track_event, which takes a dedupe_key for safe retries. |
| GET /automations | list_automations | List automations with their 30-day totals |
| POST /automations | create_automation | Create an automation as a draft |
| GET /automations/:key | get_automation | Retrieve an automation with its emails |
| PATCH /automations/:key | update_automation | Edit an automation |
| DELETE /automations/:key | delete_automation | Delete an automation and its history |
| PUT /automations/:key/steps/:position | set_automation_step | Create or change one email of an automation |
| DELETE /automations/:key/steps/:position | delete_automation_step | Remove one email from an automation |
| PUT /automations/:key/steps/:position/variants/:locale | set_automation_step_variant | Create or change a language version of an email |
| POST /automations/:key/steps/:position/test | send_automation_test_email | Send one email of an automation to yourself as a test |
| POST /automations/:key/test | send_automation_test | Send every email of an automation to yourself as tests |
| POST /automations/:key/status | set_automation_status | Turn an automation on or off |
| POST /automations/:key/enroll | enroll_contact | Add a contact to an automation |
| POST /automations/:key/exit | exit_contact | Take a contact out of an automation |
| GET /automations/:key/preview | preview_automation | Dry run: what each person in an automation would get now |
| GET /automations/overview | get_automations_overview | Totals and a daily series across every automation |
| GET /automations/:key/report | get_automation_report | Results of one automation, with one row per email |
| GET /automations/:key/people | list_automation_people | List the people in an automation by what they did |
| GET /automations/:key/people/:contact_id | get_automation_person | One person's history in an automation |
| POST /automations/:key/import-history | niet beschikbaar | History import is a one-time migration step for the account owner and requires a dashboard session. Bulk events are for server-side backfills through the REST API; an agent records what one person did with track_event, which takes a dedupe_key for safe retries. |
| GET /automation-settings | get_sending_limits | Retrieve the workspace's sending limits for automations |
| PUT /automation-settings | update_sending_limits | Change the workspace's sending limits for automations |
| GET /automation-library | list_automation_templates | List the template library: ready-made lifecycle emails |
| GET /automation-library/:id | get_automation_template | Read one template or set, with the email as it will look |
| POST /automation-library/:id/use | use_automation_template | Create a draft automation from a template or set |
| GET /events | list_events | List what contacts did, newest first |
| GET /events/names | list_event_names | List the kinds of event recorded in the last 30 days |
| POST /events/preview | niet beschikbaar | These answer the dashboard's connection and spreadsheet screens and take a request body, while this server keeps its read-only tools to GET. An agent sees what a connection did with get_connection, and what an event started with list_events. |
| GET /connections | list_connections | List the workspace's connections (incoming webhooks) |
| POST /connections | create_connection | Create a connection and get its address |
| POST /connections/test | niet beschikbaar | These answer the dashboard's connection and spreadsheet screens and take a request body, while this server keeps its read-only tools to GET. An agent sees what a connection did with get_connection, and what an event started with list_events. |
| GET /connections/:id | get_connection | Retrieve a connection with its last deliveries |
| PATCH /connections/:id | update_connection | Change a connection or switch it on or off |
| DELETE /connections/:id | delete_connection | Delete a connection |
| POST /connections/:id/address | niet beschikbaar | The address is a credential: whoever holds it can record events for the workspace. Replacing it cuts off the system that uses the old one, so a person does it in the dashboard, next to that system's own settings. |
| GET /account | get_account | Account, gebruik, factureringsstatus en aantallen in de workspace ophalen met een API-sleutel |
| GET /account/diagnostics | get_account_diagnostics | Diagnose sending and receiving problems in the workspace |
| GET /analytics | get_analytics | Verzendanalytics uit het dashboard ophalen over 7, 30 of 90 dagen |
| GET /profile | get_account | Sessievariant van GET /account; de MCP-server leest de route voor API-sleutels. |
| POST /billing/checkout | niet beschikbaar | Factureringswijzigingen kunnen bewust alleen via een sessie en vereisen de accounteigenaar in het dashboard. De factureringsstatus is leesbaar met get_account. |
| POST /billing/cancel | niet beschikbaar | Factureringswijzigingen kunnen bewust alleen via een sessie en vereisen de accounteigenaar in het dashboard. De factureringsstatus is leesbaar met get_account. |
| POST /keys | niet beschikbaar | Bewust uitgesloten: een agent mag geen credentials aanmaken of vernietigen. Sleutels worden door een mens in het dashboard beheerd. |
| GET /keys | list_api_keys | Metadata van API-sleutels opvragen |
| DELETE /keys/:id | niet beschikbaar | Bewust uitgesloten: een agent mag geen credentials aanmaken of vernietigen. Sleutels worden door een mens in het dashboard beheerd. |
Bewust niet beschikbaar
| Mogelijkheid | Endpoints | Reden |
|---|---|---|
| API-sleutels aanmaken, roteren, intrekken of verwijderen | POST /keys, DELETE /keys/:id | Bewust uitgesloten: een agent mag geen credentials aanmaken of vernietigen. Sleutels worden door een mens in het dashboard beheerd. |
| Een checkout starten of een abonnement opzeggen | POST /billing/checkout, POST /billing/cancel | Factureringswijzigingen kunnen bewust alleen via een sessie en vereisen de accounteigenaar in het dashboard. De factureringsstatus is leesbaar met get_account. |
| Cloudflare-DNS met één klik (OAuth) | GET /api/dns/cloudflare/connect | Vereist een interactieve browsersessie en toestemming via Cloudflare OAuth. Gebruik in plaats daarvan de records uit get_domain, de hosts uit get_dns_provider of get_domain_connect_link. |
| Registreren, inloggen, uitloggen, Google-account koppelen | /api/auth/* | Authenticatie door een mens in de browser; de MCP-server authenticeert met een API-sleutel. |
| Contactformulier voor support | POST /api/contact | Openbaar formulier op de marketingsite voor mensen, geen bewerking in een workspace. |
| Webhook endpoints and deliveries | GET /webhooks, POST /webhooks, GET /webhooks/:id, PATCH /webhooks/:id, DELETE /webhooks/:id, POST /webhooks/:id/rotate-secret, POST /webhooks/:id/test, GET /webhooks/:id/deliveries, GET /webhooks/:id/deliveries/:deliveryId, POST /webhooks/:id/deliveries/:deliveryId/retry | Webhook endpoints are configured once by a human, in the dashboard or the REST API, and their responses carry signing secrets an agent should not hold. An agent reads the same outcomes with list_email_events, list_emails, and list_blocked_recipients. |
| Upload editor images and export contacts as CSV | POST /uploads/images, GET /contacts/export | Image uploads take a raw binary body and the export returns a CSV file meant for a person to download. Agents reuse uploaded images with list_uploaded_images and read the same contacts, filters, tags, and fields as JSON with list_contacts (paginated). |
| Import an automation's send history and record events in bulk | POST /automations/:key/import-history, POST /events/batch | History import is a one-time migration step for the account owner and requires a dashboard session. Bulk events are for server-side backfills through the REST API; an agent records what one person did with track_event, which takes a dedupe_key for safe retries. |
| Move SendHQ's own win-back emails onto automations (backfill and comparison) | POST /automations/platform-backfill, GET /automations/platform-compare | Internal cutover tools for SendHQ's own workspace only: they answer nobody else, need its owner's dashboard session, and are not part of the public API or of /api/v1. The backfill enrols SendHQ's own accounts, so it is run by a person, one page at a time, after reading the dry run. |
| Replace a connection's secret address | POST /connections/:id/address | The address is a credential: whoever holds it can record events for the workspace. Replacing it cuts off the system that uses the old one, so a person does it in the dashboard, next to that system's own settings. |
| Dry runs for a sample payload and for a set of events | POST /connections/test, POST /events/preview | These answer the dashboard's connection and spreadsheet screens and take a request body, while this server keeps its read-only tools to GET. An agent sees what a connection did with get_connection, and what an event started with list_events. |
Machineleesbare catalogus: /docs/mcp/tools.json (schema's, annotaties, koppeling met endpoints, uitzonderingen). Markdownversie van deze pagina: /docs/mcp.md. Met de CLI geïnstalleerd print sendhq commands --format json dezelfde catalogus.