Email

Make this account's domains for one provider account match the list given — connecting the ones that are missing and REMOVING every connected domain from that account that is not in the list. The omission is the instruction, so sending a partial list silently drops the rest: read email.review_account_domains first and send back the full set you want to end up with. Connecting a domain registers Chirply on that domain's delivery-event webhooks inside the customer's own provider account, alongside anything already there; removing one takes those webhooks and the inbound route Chirply added back out, while leaving the customer's own webhooks and their open and click tracking untouched. Domains stay in the provider account either way — only their connection to this account changes. A domain being removed that still has account addresses is SKIPPED and reported rather than removed, unless remove_addresses is set. Never turns receiving on: a newly connected domain sends only until someone chooses where its mail should arrive. Each domain succeeds or fails on its own and the response reports both.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.apply_account_domains \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "keep": [
      {
        "domain": "example"
      }
    ]
  }'

Over MCP the same operation is the tool email_apply_account_domains at https://app.chirply.io/api/mcp, same bearer token, same input.

Run a deliverability health check on the account's connected email sending domains: provider verification, SPF, DKIM, DMARC policy, whether the domain can receive replies (MX), and its sending reputation. SPF/DKIM come from the provider's own verification; DMARC and MX are looked up in public DNS. Reputation is graded from bounce, spam-complaint and open rates over the last 30 days — from this account's own send history where there is enough of it, otherwise from the provider's own totals for the domain, which cover ALL mail sent from it including mail not sent through Chirply. Read-only and free — it queries DNS and the provider API, sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.check_domain_health \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_check_domain_health at https://app.chirply.io/api/mcp, same bearer token, same input.

Check whether every account address that is set to receive replies can actually be reached, and report the ones that cannot. A saved inbound provider is not enough on its own: if the domain's MX records still deliver mail to Google, Microsoft or its own mail server, incoming mail never reaches the platform and every reply is silently lost while the address still reads as receiving. Names where each broken domain's mail is going today and whether the DNS can be repaired automatically. Read-only — reads public DNS and the account's own Cloudflare zone list, changes nothing, and returns no provider secrets.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.check_receiving \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool email_check_receiving at https://app.chirply.io/api/mcp, same bearer token, same input.

Connect several sending domains from ONE Mailgun or Resend account in a single call, and optionally create the From addresses to send as on each. Every domain is verified with the provider before it is saved; the API key is encrypted at rest. This also changes settings inside its own provider account — it registers delivery webhooks, switches open tracking on, and, for domains marked to receive, points the provider's inbound route at this account so replies land in Conversations. Sends no email and spends no money by itself; the account's provider still bills any mail later sent through it.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.connect_domains \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "mailgun",
    "api_key": "example",
    "domains": [
      {
        "domain": "example"
      }
    ]
  }'

Over MCP the same operation is the tool email_connect_domains at https://app.chirply.io/api/mcp, same bearer token, same input.

Connect another Mailgun or Resend account to this account. The supplied API key is verified with the provider and encrypted before storage, and connecting changes settings inside the customer's own provider account: it registers delivery-event webhooks and switches open tracking on. When the Mailgun account being connected is (or becomes) this account's primary Mailgun connection, the inbound mail route is provisioned in that Mailgun account too — the same step the app performs — so replies to the connected domain land in Conversations instead of vanishing. This does not send email or create provider charges by itself.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.connect_provider \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "mailgun",
    "label": "example",
    "domain": "example",
    "api_key": "example"
  }'

Over MCP the same operation is the tool email_connect_provider at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a selectable account From address on a verified Mailgun or Resend connection and optionally route inbound mail through a different connected provider. Sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.create_identity \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "ada@example.com",
    "outbound_connection_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_create_identity at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete one account From address. The provider connection, its domain and every other address on it are left alone — only this sender is removed. Past conversations, campaigns and messages keep their history but lose their pinned sender, so their next reply goes out from the account default instead, changing what those recipients see. If the address belongs to any sending pool it is dropped from that rotation, concentrating the volume on the pool's remaining members. The account default sender cannot be deleted while another address could take over, because it is what brands authentication email such as password resets.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.delete_identity \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_delete_identity at https://app.chirply.io/api/mcp, same bearer token, same input.

Throw away one AI-written email reply so it is never sent. The contact hears nothing back from the agent on that message; a person can still write their own reply. The text is kept on the record as what the agent wanted to say.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.discard_ai_draft \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "reply_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_discard_ai_draft at https://app.chirply.io/api/mcp, same bearer token, same input.

Remove one sending domain from this account and undo what connecting it did inside the customer's own Mailgun or Resend account. This is not only a local delete: it takes Chirply's delivery-event webhooks off that domain and deletes the inbound route this account added, so the provider stops sending that domain's traffic here. Registrations Chirply did not create — the customer's own application's webhooks, another account's — are preserved, and open and click tracking are left exactly as they are. The domain itself stays in the provider account, verified and able to send; only its connection to this account ends. Refuses while account addresses still send through the domain unless remove_addresses is set, in which case those addresses are deleted too and drop out of any rotation pools they belong to, shrinking those pools. Past conversations and campaigns keep their history and fall back to the account default sender. Cannot be undone from here — reconnecting means pasting the provider API key again.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.disconnect_domain \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_disconnect_domain at https://app.chirply.io/api/mcp, same bearer token, same input.

List every sending domain that already exists inside a Mailgun or Resend account, using an API key supplied with the call, and mark which of them this account has already connected. This is the lookup behind 'paste one key, pick your domains': the key is used for this read and discarded, nothing is stored, and no provider secret is returned. Costs nothing and sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.discover_domains \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "mailgun",
    "api_key": "example"
  }'

Over MCP the same operation is the tool email_discover_domains at https://app.chirply.io/api/mcp, same bearer token, same input.

Show what mailbox providers have reported back about mail claiming to be from this account's sending domains, over the last 30 days. DMARC aggregate reports come from the RECEIVERS — Google, Microsoft, Yahoo and everyone else — so unlike delivery statistics they cover every provider and include mail this account did not send. For each domain: how many messages were seen, how many passed authentication, how many were sent to spam or rejected, the DMARC policy currently published, which receivers reported, and the sending IPs that FAILED authentication with the domains they signed as. A failing source is usually a legitimate service missing from the domain's SPF or DKIM records; one nobody recognises is someone sending as the domain. Read-only and free — it reads reports already received, contacts nobody and sends nothing. Owner/admin only, matching the Email pools settings screen.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.dmarc_summary \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "days": 30
  }'

Over MCP the same operation is the tool email_dmarc_summary at https://app.chirply.io/api/mcp, same bearer token, same input.

Switch open tracking on for the account's connected Mailgun or Resend accounts, so the provider inserts its tracking pixel and reports opens. This changes a setting inside its OWN provider account and applies to every email that account sends, including mail sent by other tools using the same domain. Click tracking is deliberately left alone. Sends nothing and costs nothing.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.enable_open_tracking \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_enable_open_tracking at https://app.chirply.io/api/mcp, same bearer token, same input.

Rewrite a receiving domain's MX records in its own connected Cloudflare account so incoming mail is delivered to the platform instead of wherever it goes now. THIS TAKES OVER ALL MAIL FOR THAT DOMAIN AND IS NOT LIMITED TO THIS ONE ADDRESS: every existing mailbox behind the domain's current mail servers — staff inboxes, a helpdesk, anything else — stops receiving the moment DNS propagates, and the displaced records are deleted, not kept. Only run this when the person owning the domain understands they are moving its mail. Requires a connected Cloudflare account that holds the zone; it fails cleanly with the records to add by hand otherwise. Changing the MX back is a manual DNS edit at their provider.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.fix_receiving_dns \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_fix_receiving_dns at https://app.chirply.io/api/mcp, same bearer token, same input.

List the email replies an AI agent has written that are still waiting for a person to approve or discard, with the agent that wrote each one, the address it would go out from, and the full text. Read-only; sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.list_ai_drafts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "conversation_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_list_ai_drafts at https://app.chirply.io/api/mcp, same bearer token, same input.

List the account's connected Mailgun and Resend accounts, their verified domains, connection state, and whether inbound authentication is configured. Read-only; returns no provider secrets.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.list_connections \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool email_list_connections at https://app.chirply.io/api/mcp, same bearer token, same input.

List every ready or pending account email identity — the From addresses this account can send as — with its Mailgun/Resend routing, display name, reply-to and which one is the account default. This is the list the inbox and broadcast composers' sender pickers show, so any member can read it. Read-only; returns no provider secrets.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.list_identities \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool email_list_identities at https://app.chirply.io/api/mcp, same bearer token, same input.

List the Mailgun and Resend ACCOUNTS this account holds credentials for, with the domains from each one that are currently connected and the account addresses on them. Connections are stored one per domain, so this groups them back into the account a person actually connected — which is the unit email.review_account_domains re-queries. Each account is identified by a non-reversible fingerprint of its API key; no key or secret is ever returned. Read-only.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.list_provider_accounts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool email_list_provider_accounts at https://app.chirply.io/api/mcp, same bearer token, same input.

Re-register the delivery-event webhooks for a sending domain your AGENCY provides, so opens, clicks, deliveries, bounces and spam complaints are recorded against this account again. Only affects an agency-provided (pooled) email connection — an account that connected its own Mailgun or Resend already does this when it connects, and this leaves it alone. It writes a webhook into the agency's own provider account alongside anything already there, never replacing it, and it is safe to run repeatedly: a domain already registered reports that and does nothing. Sends no email and costs nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.repair_delivery_events \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "force": false
  }'

Over MCP the same operation is the tool email_repair_delivery_events at https://app.chirply.io/api/mcp, same bearer token, same input.

Take one sending address out of pool rotation for a few days so its reputation can recover — the right response to a spiking bounce or spam-complaint rate. While resting, bulk sends through any pool skip this address and lean on the pool's other members, which concentrates the same volume on them; one-to-one replies and direct sends from the address still go out, so nobody mid-conversation is cut off. Pass 0 days to end a rest immediately and put the address straight back in the rotation. Reversible at any time; sends nothing and costs nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.rest_sender \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "days": 1
  }'

Over MCP the same operation is the tool email_rest_sender at https://app.chirply.io/api/mcp, same bearer token, same input.

Ask a connected Mailgun or Resend account what sending domains it holds RIGHT NOW, and report each one beside whether this account has it connected. Uses the API key already stored for that account, so nothing needs pasting; the key is used for the provider call and never returned. Also names domains this account still holds that the account no longer lists at all — deleted at the provider, or no longer covered by that key. Read-only: it changes nothing here and nothing in the provider account. Use email.apply_account_domains to act on the result.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.review_account_domains \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_review_account_domains at https://app.chirply.io/api/mcp, same bearer token, same input.

Approve one AI-written email reply and send it immediately to the contact, as real email from its own Mailgun or Resend account — billed to them, and impossible to recall once gone. Optionally replace the subject or body first, in which case the edited text is what is sent and what is kept on the record.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.send_ai_draft \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "reply_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_send_ai_draft at https://app.chirply.io/api/mcp, same bearer token, same input.

Immediately sends one real test email through the selected account Mailgun or Resend identity to the requested recipient. The account's provider may charge for this delivery.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.send_test \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "recipient": "ada@example.com"
  }'

Over MCP the same operation is the tool email_send_test at https://app.chirply.io/api/mcp, same bearer token, same input.

Show how warm and how healthy every account sending address is, from what the email provider actually reported over the last 30 days. Each address gets a temperature — cold (no recent history, inbox providers have nothing to go on), warming (ramping, or sending below the volume of an established sender), warm (established and safe for normal campaign volume) or hot (sustaining high daily volume) — plus its bounce rate, spam-complaint rate, open rate, a reputation verdict, and a one-line answer to 'is this good to send from?'. Also reports any address currently resting. Read-only and free: it reads the account's own send history, contacts no provider and sends nothing. Owner/admin only, matching the Email pools settings screen.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.sender_health \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_sender_health at https://app.chirply.io/api/mcp, same bearer token, same input.

Show today's send count for every account email address alongside its effective bulk daily cap (warmup allowance and any automatic reputation slow-down combined; null when uncapped), so you can see which senders have headroom left and which have been slowed down for high bounce/complaint rates — and exactly why. Counts reset at midnight UTC. Read-only. Owner/admin only, matching the Email pools settings screen this table appears on.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.sender_usage \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool email_sender_usage at https://app.chirply.io/api/mcp, same bearer token, same input.

Choose who answers email sent to one account address: nobody, or one of the account's AI agents. In draft mode the agent writes a reply that waits in the conversation until a person reads it and presses Send — nothing leaves the address on its own. In send mode the agent answers real people from that address, unattended, with nobody checking first; those replies are real email billed to its own Mailgun or Resend account and cannot be recalled. The agent never answers bounces, out-of-office notices, mailing lists or no-reply addresses, and never someone who asked to unsubscribe. The address must already be set up to receive mail, and the agent must be active. Changes take effect on the next email that arrives.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.set_ai_replies \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "mode": "off"
  }'

Over MCP the same operation is the tool email_set_ai_replies at https://app.chirply.io/api/mcp, same bearer token, same input.

Make this address the account's default From. It is used for two things: any email that doesn't name its own sender, and the account's authentication email — password resets, invitations and address confirmations are branded with it, so recipients see this address on the messages that get people into the account. Existing conversations keep their sticky identity, and contact-specific preferences still win. Only one address can be the default, so this replaces the current one. Sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.set_default_identity \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_set_default_identity at https://app.chirply.io/api/mcp, same bearer token, same input.

Hand one of the account's email addresses to a named teammate, or hand it back to the whole team. This is a routing decision, not a permission: from then on, mail arriving at that address is assigned to that person in the shared inbox and it becomes the address they send from by default, while every teammate who could already read the inbox still can. The person must already be a member of this account. Existing conversations that somebody has already been assigned are left alone; unassigned ones are picked up as new mail arrives. Sends nothing and changes no message.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.set_identity_owner \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "owner_user_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_set_identity_owner at https://app.chirply.io/api/mcp, same bearer token, same input.

Turn open tracking and click tracking on or off for ONE connected Mailgun or Resend account. This changes the setting inside its own provider account, so it applies to every email that account sends from that domain — including mail sent by other tools using the same domain, and including mail already queued. Turning open tracking off stops the provider inserting its invisible tracking pixel, so opens stop being recorded for recipients from that moment on; turning it on starts recording them. For Resend this also names the tracking subdomain and publishes its CNAME in the account's own DNS, because Resend applies neither flag until that record verifies. Sends no email and costs nothing.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.set_tracking \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "open": true,
    "click": true
  }'

Over MCP the same operation is the tool email_set_tracking at https://app.chirply.io/api/mcp, same bearer token, same input.

Turn a warmup ramp on or off for one account email address. While warming, pool rotation caps that sender at its current daily allowance (start volume + increment per elapsed day, leveling off at the maximum, counted per UTC day). Direct sends from the address are still counted but not blocked. Changes future pacing only; sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.set_warmup \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "enabled": true
  }'

Over MCP the same operation is the tool email_set_warmup at https://app.chirply.io/api/mcp, same bearer token, same input.

Report, for each connected Mailgun or Resend account, whether the provider is currently tracking email opens and clicks. Read-only; asks the provider directly rather than reporting a stored value, so it is the way to tell 'nobody opened it' apart from 'nothing was tracking it'. Returns no provider secrets.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.tracking_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool email_tracking_status at https://app.chirply.io/api/mcp, same bearer token, same input.

Update the visible From address, friendly From name, and Reply-to address for an existing account email identity. A changed From address must stay on the identity's connected sending domain (and its receiving domain when inbound mail is enabled). This changes what future recipients see and where their replies are delivered; it sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.update_identity \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_update_identity at https://app.chirply.io/api/mcp, same bearer token, same input.

Change which connected provider sends and receives for an existing account email identity. Sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email.update_identity_routing \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "outbound_connection_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_update_identity_routing at https://app.chirply.io/api/mcp, same bearer token, same input.