SendFox

Remove an email from an automation via DELETE /automation-emails/{id}

Delete an automation -- Soft-deletes the automation and cancels all scheduled deliverables via DELETE /automations/{id}

Delete a draft campaign -- Only draft campaigns (not yet sent) can be deleted. Uses soft delete. via DELETE /campaigns/{id}

Delete a contact field -- Permanently deletes the contact field via DELETE /contact-fields/{id}

Delete a contact tag -- Deletes the tag. Tagged contacts are kept — only the tag and its attachments (including campaign audience use) are removed. via DELETE /contact-tags/{id}

Remove a tag from a contact via DELETE /contacts/{contact_id}/tags/{tag_id}

Delete a contact -- Soft-deletes a contact and cancels any scheduled deliverables via DELETE /contacts/{id}

Delete a sender domain -- Removes the domain from SendGrid and soft-deletes locally via DELETE /domains/{id}

Delete a form -- Soft-deletes the form via DELETE /forms/{id}

Delete a contact list -- Soft-deletes a list. Returns 409 if the list is used by forms, landing pages, or automations. via DELETE /lists/{id}

Remove a contact from a list via DELETE /lists/{list_id}/contacts/{contact_id}

List automations via GET /automations

Get a specific automation -- Returns automation with triggers, items, and campaign stats via GET /automations/{id}

List saved campaign sections -- Returns only content owned by the authenticated account, including saved HTML. Shared gallery content is not included. This endpoint does not publish, modify or send content. Results are ordered by descending ID, 20 per page. via GET /campaign-sections

Get a saved campaign section -- Returns only content owned by the authenticated account, including saved HTML. Shared gallery content is not included. This endpoint does not publish, modify or send content. via GET /campaign-sections/{id}

List saved campaign templates -- Returns only content owned by the authenticated account, including saved HTML. Shared gallery content is not included. This endpoint does not publish, modify or send content. Results are ordered by descending ID, 20 per page. via GET /campaign-templates

Get a saved campaign template -- Returns only content owned by the authenticated account, including saved HTML. Shared gallery content is not included. This endpoint does not publish, modify or send content. via GET /campaign-templates/{id}

List campaigns -- Returns a paginated list of campaigns (100 per page) via GET /campaigns

Get a specific campaign via GET /campaigns/{id}

List the contacts behind a campaign's engagement -- Returns the contacts in one of a sent campaign's engagement groups. non_openers covers contacts the campaign actually sent to who did not open it — queued and cancelled deliverables are excluded, since they never had the chance. via GET /campaigns/{id}/engagement

Get campaign performance statistics -- Returns sent count and open/click/bounce/unsubscribe/spam counts and rates, all read from stored counters. Pass `include_link_stats=true` to also get `link_stats` — the campaign's links ranked by click count. That part is opt-in because it counts rows in `email_link_clicks` once per link rather than reading a counter, so leaving it off keeps this endpoint as cheap as it has always been. via GET /campaigns/{id}/stats

Get statistics for multiple campaigns -- Returns stored counts and rates for one to 100 distinct owned campaigns in request order. The entire request fails with the same validation error for missing, deleted or foreign IDs. Does not return link stats or query individual delivery events. via GET /campaigns/stats

List user contact fields -- Returns custom contact fields defined by the user (20 per page) via GET /contact-fields

Get a specific contact field via GET /contact-fields/{id}

List contact tags -- Lists the account's tags, newest first, each with its contact count. Distinct from the legacy /tags endpoints, which operate on lists. via GET /contact-tags

Get a contact tag via GET /contact-tags/{id}

List contacts -- Returns a paginated list of contacts (100 per page by default, up to 1000 via `per_page`). Supports engagement filtering through `filter[...]` query parameters, so you can answer questions like "who last opened over a year ago" without paging the whole account. All filter conditions are AND-ed. Pass `count_only=true` to get just the number of matches — the cheapest way to size an audience before acting on it. via GET /contacts

Check the progress of a bulk contact action -- For a dry run, matched_count is the answer and nothing was modified. A run whose match set exceeds the per-request ceiling fails without applying anything. via GET /contacts/bulk-actions/{id}

List a contact's tags via GET /contacts/{contact_id}/tags

Get a specific contact via GET /contacts/{id}

Get email activity for a contact -- Returns paginated email deliverables and contact-level engagement summary via GET /contacts/{id}/activity

List unsubscribed contacts via GET /contacts/unsubscribed

List sender domains -- Returns a paginated list of the user's whitelabel/sender domains via GET /domains

Get domain with DNS records -- Returns domain details including DNS records needed for verification via GET /domains/{id}

List forms via GET /forms

Get a specific form via GET /forms/{id}

List contact lists via GET /lists

Get a specific contact list -- Returns list details including average open and click rates via GET /lists/{id}

Get contacts in a list via GET /lists/{list_id}/contacts

Get current user information via GET /me

Update an automation email via PATCH /automation-emails/{id}

Update an automation -- Update title, trigger, or active status. Activating reschedules stale deliverables. via PATCH /automations/{id}

Update a draft campaign -- Only draft campaigns (not yet sent) can be updated. All fields are optional. via PATCH /campaigns/{id}

Update a contact field label -- Updates the label and auto-regenerates the name slug. Note: `contact_field_type_id` is immutable and cannot be changed after creation. via PATCH /contact-fields/{id}

Update a contact tag via PATCH /contact-tags/{id}

Update a contact -- Update contact details including name, list memberships, and custom fields via PATCH /contacts/{id}

Update a form via PATCH /forms/{id}

Update a contact list via PATCH /lists/{id}

Unsubscribe a contact by email via PATCH /unsubscribe

Create an automation via POST /automations

Add an email to an automation via POST /automations/{id}/emails

Create a new campaign -- Creates a campaign as a draft. To send it, use the send endpoint or provide scheduled_at. Subject lines cannot start with "RE:" or "FWD:". At least one list is required if scheduled_at is provided. via POST /campaigns

Clone a sent campaign at part of its original audience -- Creates a new draft with the original's content, sender, and exclusions, aimed at the chosen slice of the original audience. Omit scheduled_at to leave it as a draft. The source campaign's lists are deliberately not carried over — the engagement segment is the audience. via POST /campaigns/{id}/resend

Send a campaign immediately -- Schedules a draft campaign for immediate sending. The campaign must: - Not already be sent or scheduled - Have at least one list assigned - Not be a confirmation (double opt-in) email — those are delivered to each contact as they subscribe, never as a broadcast - The user must not be in a warmup/throttle period All existing abuse prevention applies automatically: content approval workflow, sending throttles, spam detection, and bounce rate monitoring. via POST /campaigns/{id}/send

Create a custom contact field -- Creates a custom field for contacts. The `name` is auto-generated from the `label` as a slug. Provide `type` (`text`, `number`, or `date`) or the existing `contact_field_type_id` UUID. If both are provided, they must identify the same type. UUIDs are the same for every account: | Type | `contact_field_type_id` | | ------ | -------------------------------------- | | text | `0abe5601-7738-43c8-858f-81911ecf89ee` | | number | `e43c6471-b3ff-4541-80c5-964c62decd15` | | date | `fe7dd76c-5113-4159-bc7c-0dbf0ed8d404` | The value is immutable after creation and is not returned by any endpoint - responses carry the human-readable `type` (`text`, `number`, `date`) instead. via POST /contact-fields

Create a contact tag -- Creates a tag. A brand color is auto-assigned when none is provided. Tag names are unique per account. via POST /contact-tags

Create a new contact via POST /contacts

Batch import contacts -- Import up to 1,000 contacts in a single request. Creates new contacts or updates existing ones. via POST /contacts/batch

Apply a tag or list change to every contact matching a filter -- Queues one action against every contact the filter matches, applied in chunks in the background. Returns immediately with an id to poll. **Run with `dry_run: true` first.** A dry run reports how many contacts match and changes nothing — it is the only way to catch a filter that matches more than intended, and a bulk write is not undoable. An empty filter (which would match the whole account) is rejected unless it is a dry run. Per-campaign conditions (`opened_campaign_id`, `not_opened_campaign_id`, `clicked_campaign_id`) are available here but not on `GET /contacts`, because they are resolved in the background rather than inside a request. Bulk delete and bulk unsubscribe are deliberately not offered. via POST /contacts/bulk-actions

Attach a tag to a contact -- Idempotent. Returns the contact's tags after the change. via POST /contacts/{contact_id}/tags/{tag_id}

Add a sender domain -- Adds a new sender domain and creates the corresponding SendGrid whitelabel domain. Requires an active subscription and SendGrid subuser. via POST /domains

Validate domain DNS records -- Triggers DNS validation for the domain via SendGrid. Returns whether validation passed and any errors for specific DNS records. via POST /domains/{id}/validate

Create a new form -- Creates a subscription form linked to one or more lists. Free users are limited to 1 form. via POST /forms

Create a new contact list via POST /lists

Add a contact to a list -- Adds an existing contact to a list. If the contact is already in the list, no duplicate is created. via POST /lists/{list_id}/contacts