Skip to content

API reference

Every Email Marketing API endpoint, with examples.

Check a key

GET/marketing/v1/me

The account a key belongs to and what it may do. Any key can call it: use it to check a key when someone connects your app.

GET/marketing/v1/me
curl -X GET 'https://api.iresendly.com/marketing/v1/me' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "account",
  "id": "usr_9f2c",
  "name": "Jane's Shop",
  "email": "owner@example.com",
  "plan": "standard",
  "contact_limit": 5000,
  "key": {
    "id": "6736…",
    "name": "SellOrchard",
    "scopes": [
      "contacts:read",
      "contacts:write",
      "lists:read",
      "lists:write"
    ]
  }
}

Create or update a contact

POST/marketing/v1/contactscontacts:write

Creates the contact, or updates it when one already has the same external_id or email. Tags and lists are added to what the contact already has. A refused address answers 422 with its reason; a full account answers 403 contact_limit.

Body
  • emailstringrequired

    The contact's email address. New and changed addresses go through the same checks as an import.

  • external_idstring

    Your own id for this person, such as a store's customer id. Matched first, so a changed email updates the same contact. Unique in your account.

  • first_namestring

    First name.

  • last_namestring

    Last name.

  • phonestring

    Phone number.

  • subscribedboolean

    false unsubscribes the contact. true (or leaving it out) subscribes a new contact, but never re-subscribes one who unsubscribed, bounced or complained.

  • custom_fieldsobject

    Up to 50 fields. Names start with a letter and use letters, numbers and _. Values are text, numbers, true/false or null. Merged into the contact's fields.

  • tagsstring[]

    Tag names to add. Missing tags are created. Matched without regard to case.

  • list_idsstring[]

    Lists to add the contact to, by id.

  • list_keysstring[]

    Lists to add the contact to, by your own list key (create them with POST /lists first).

POST/marketing/v1/contacts
curl -X POST 'https://api.iresendly.com/marketing/v1/contacts' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Idempotency-Key: order-1042-customer' \
  -H 'Content-Type: application/json' \
  -d '{
  "email": "jane@example.com",
  "external_id": "cus_1042",
  "first_name": "Jane",
  "tags": [
    "Customer"
  ],
  "list_keys": [
    "segment_vip"
  ],
  "custom_fields": {
    "orders_count": 3
  }
}'
Response
{
  "object": "contact",
  "id": "6736a1f0c2a4e51d2f0b7c11",
  "email": "jane@example.com",
  "external_id": "cus_1042",
  "first_name": "Jane",
  "last_name": "Doe",
  "phone": null,
  "status": "active",
  "subscribed": true,
  "tags": [
    "Customer",
    "VIP"
  ],
  "list_ids": [
    "6736a1c4c2a4e51d2f0b7c0a"
  ],
  "custom_fields": {
    "orders_count": 3
  },
  "source": "api",
  "created_at": "2026-11-14T10:12:00.000Z",
  "updated_at": "2026-11-14T10:12:00.000Z",
  "outcome": "created"
}

Create or update contacts in a batch

POST/marketing/v1/contacts/batchcontacts:write

Up to 100 contacts, each with the same fields as a single contact and answered on its own: a refused contact is skipped with its reason, and the rest still go in.

Body
  • contactsobject[]required

    The contacts (1–100).

POST/marketing/v1/contacts/batch
curl -X POST 'https://api.iresendly.com/marketing/v1/contacts/batch' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "contacts": [
    {
      "email": "jane@example.com",
      "external_id": "cus_1042"
    },
    {
      "email": "info@example.com"
    }
  ]
}'
Response
{
  "object": "batch",
  "created": 1,
  "updated": 0,
  "skipped": 1,
  "results": [
    {
      "index": 0,
      "email": "jane@example.com",
      "outcome": "created",
      "id": "6736a1f0c2a4e51d2f0b7c11"
    },
    {
      "index": 1,
      "email": "info@example.com",
      "outcome": "skipped",
      "reason": "address",
      "message": "Role-based addresses aren't accepted"
    }
  ]
}

List contacts

GET/marketing/v1/contactscontacts:read

Newest first. Use after with the last id of a page to get the next one.

Query parameters
  • limitnumber

    1–100, default 50.

  • afterstring

    A contact id: the page after it.

  • beforestring

    A contact id: the page before it.

  • emailstring

    Only this email address.

  • external_idstring

    Only this external id.

  • list_idstring

    Only members of this list.

  • list_keystring

    Only members of the list with this key.

  • tagstring

    Only contacts with this tag name.

  • statusstring

    active, unsubscribed, bounced, complained, suppressed, invalid or pending.

GET/marketing/v1/contacts
curl -X GET 'https://api.iresendly.com/marketing/v1/contacts' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "has_more": false,
  "data": [
    {
      "object": "contact",
      "id": "6736a1f0c2a4e51d2f0b7c11",
      "email": "jane@example.com",
      "external_id": "cus_1042",
      "first_name": "Jane",
      "last_name": "Doe",
      "phone": null,
      "status": "active",
      "subscribed": true,
      "tags": [
        "Customer",
        "VIP"
      ],
      "list_ids": [
        "6736a1c4c2a4e51d2f0b7c0a"
      ],
      "custom_fields": {
        "orders_count": 3
      },
      "source": "api",
      "created_at": "2026-11-14T10:12:00.000Z",
      "updated_at": "2026-11-14T10:12:00.000Z"
    }
  ]
}

Get a contact

GET/marketing/v1/contacts/{id}contacts:read

One contact by its iResendly id.

Path parameters
  • idstringrequired

    The contact id.

GET/marketing/v1/contacts/{id}
curl -X GET 'https://api.iresendly.com/marketing/v1/contacts/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "contact",
  "id": "6736a1f0c2a4e51d2f0b7c11",
  "email": "jane@example.com",
  "external_id": "cus_1042",
  "first_name": "Jane",
  "last_name": "Doe",
  "phone": null,
  "status": "active",
  "subscribed": true,
  "tags": [
    "Customer",
    "VIP"
  ],
  "list_ids": [
    "6736a1c4c2a4e51d2f0b7c0a"
  ],
  "custom_fields": {
    "orders_count": 3
  },
  "source": "api",
  "created_at": "2026-11-14T10:12:00.000Z",
  "updated_at": "2026-11-14T10:12:00.000Z"
}

Update a contact

PATCH/marketing/v1/contacts/{id}contacts:write

The same fields and rules as creating one (all optional), plus taking tags and lists off.

Path parameters
  • idstringrequired

    The contact id.

Body
  • emailstring

    The contact's email address. New and changed addresses go through the same checks as an import.

  • external_idstring

    Your own id for this person, such as a store's customer id. Matched first, so a changed email updates the same contact. Unique in your account.

  • first_namestring

    First name.

  • last_namestring

    Last name.

  • phonestring

    Phone number.

  • subscribedboolean

    false unsubscribes the contact. true (or leaving it out) subscribes a new contact, but never re-subscribes one who unsubscribed, bounced or complained.

  • custom_fieldsobject

    Up to 50 fields. Names start with a letter and use letters, numbers and _. Values are text, numbers, true/false or null. Merged into the contact's fields.

  • tagsstring[]

    Tag names to add. Missing tags are created. Matched without regard to case.

  • list_idsstring[]

    Lists to add the contact to, by id.

  • list_keysstring[]

    Lists to add the contact to, by your own list key (create them with POST /lists first).

  • remove_tagsstring[]

    Tag names to take off.

  • remove_list_idsstring[]

    Lists to take the contact off, by id.

  • remove_list_keysstring[]

    Lists to take the contact off, by key.

PATCH/marketing/v1/contacts/{id}
curl -X PATCH 'https://api.iresendly.com/marketing/v1/contacts/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "last_name": "Smith",
  "remove_tags": [
    "Trial"
  ]
}'
Response
{
  "object": "contact",
  "id": "6736a1f0c2a4e51d2f0b7c11",
  "email": "jane@example.com",
  "external_id": "cus_1042",
  "first_name": "Jane",
  "last_name": "Smith",
  "phone": null,
  "status": "active",
  "subscribed": true,
  "tags": [
    "Customer",
    "VIP"
  ],
  "list_ids": [
    "6736a1c4c2a4e51d2f0b7c0a"
  ],
  "custom_fields": {
    "orders_count": 3
  },
  "source": "api",
  "created_at": "2026-11-14T10:12:00.000Z",
  "updated_at": "2026-11-14T10:12:00.000Z"
}

Unsubscribe a contact

POST/marketing/v1/contacts/{id}/unsubscribecontacts:write

Always works. Only the person can subscribe again, from a sign-up form or the preference page.

Path parameters
  • idstringrequired

    The contact id.

POST/marketing/v1/contacts/{id}/unsubscribe
curl -X POST 'https://api.iresendly.com/marketing/v1/contacts/{id}/unsubscribe' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "contact",
  "id": "6736a1f0c2a4e51d2f0b7c11",
  "email": "jane@example.com",
  "external_id": "cus_1042",
  "first_name": "Jane",
  "last_name": "Doe",
  "phone": null,
  "status": "unsubscribed",
  "subscribed": false,
  "tags": [
    "Customer",
    "VIP"
  ],
  "list_ids": [
    "6736a1c4c2a4e51d2f0b7c0a"
  ],
  "custom_fields": {
    "orders_count": 3
  },
  "source": "api",
  "created_at": "2026-11-14T10:12:00.000Z",
  "updated_at": "2026-11-14T10:12:00.000Z"
}

Delete a contact

DELETE/marketing/v1/contacts/{id}contacts:write

Deletes the contact from the account.

Path parameters
  • idstringrequired

    The contact id.

DELETE/marketing/v1/contacts/{id}
curl -X DELETE 'https://api.iresendly.com/marketing/v1/contacts/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "contact",
  "id": "6736a1f0c2a4e51d2f0b7c11",
  "deleted": true
}

Create or update a list

POST/marketing/v1/listslists:write

Creates a list. With a key that already exists, that list is renamed and returned instead, so you can call this every time you sync. Lists with a key show Synced from your key's name in iResendly, and only you change their members and name.

Body
  • namestringrequired

    The list's name.

  • keystring

    Your own key for the list, such as a segment id. Unique in the account.

  • descriptionstring

    A description.

POST/marketing/v1/lists
curl -X POST 'https://api.iresendly.com/marketing/v1/lists' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "name": "VIP customers",
  "key": "segment_vip"
}'
Response
{
  "object": "list",
  "id": "6736a1c4c2a4e51d2f0b7c0a",
  "key": "segment_vip",
  "name": "VIP customers",
  "description": null,
  "contact_count": 128,
  "synced_by": "SellOrchard",
  "created_at": "2026-11-14T10:10:00.000Z",
  "updated_at": "2026-11-14T10:10:00.000Z",
  "outcome": "created"
}

List lists

GET/marketing/v1/listslists:read

Every list in the account, newest first.

GET/marketing/v1/lists
curl -X GET 'https://api.iresendly.com/marketing/v1/lists' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "has_more": false,
  "data": [
    {
      "object": "list",
      "id": "6736a1c4c2a4e51d2f0b7c0a",
      "key": "segment_vip",
      "name": "VIP customers",
      "description": null,
      "contact_count": 128,
      "synced_by": "SellOrchard",
      "created_at": "2026-11-14T10:10:00.000Z",
      "updated_at": "2026-11-14T10:10:00.000Z"
    }
  ]
}

Get a list

GET/marketing/v1/lists/{id}lists:read

By id, or by key as key:<your key>.

Path parameters
  • idstringrequired

    The list id, or key:segment_vip.

GET/marketing/v1/lists/{id}
curl -X GET 'https://api.iresendly.com/marketing/v1/lists/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "id": "6736a1c4c2a4e51d2f0b7c0a",
  "key": "segment_vip",
  "name": "VIP customers",
  "description": null,
  "contact_count": 128,
  "synced_by": "SellOrchard",
  "created_at": "2026-11-14T10:10:00.000Z",
  "updated_at": "2026-11-14T10:10:00.000Z"
}

Update a list

PATCH/marketing/v1/lists/{id}lists:write

Rename a list or change its description.

Path parameters
  • idstringrequired

    The list id, or key:<your key>.

Body
  • namestring

    New name.

  • descriptionstring

    New description, or null.

PATCH/marketing/v1/lists/{id}
curl -X PATCH 'https://api.iresendly.com/marketing/v1/lists/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "name": "VIP (spent over $500)"
}'
Response
{
  "object": "list",
  "id": "6736a1c4c2a4e51d2f0b7c0a",
  "key": "segment_vip",
  "name": "VIP (spent over $500)",
  "description": null,
  "contact_count": 128,
  "synced_by": "SellOrchard",
  "created_at": "2026-11-14T10:10:00.000Z",
  "updated_at": "2026-11-14T10:10:00.000Z"
}

Delete a list

DELETE/marketing/v1/lists/{id}lists:write

Only lists created through the API. Contacts stay; they just leave the list.

Path parameters
  • idstringrequired

    The list id, or key:<your key>.

DELETE/marketing/v1/lists/{id}
curl -X DELETE 'https://api.iresendly.com/marketing/v1/lists/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "id": "6736a1c4c2a4e51d2f0b7c0a",
  "deleted": true
}

Add or remove list members

POST/marketing/v1/lists/{id}/memberslists:write

Up to 1,000 existing contacts at a time, by id, email or external id. To set a list's members to exactly a set of people, use an import with replace_list_members.

Path parameters
  • idstringrequired

    The list id, or key:<your key>.

Body
  • actionstringrequired

    add or remove.

  • contact_idsstring[]

    Contact ids.

  • emailsstring[]

    Email addresses.

  • external_idsstring[]

    Your external ids.

POST/marketing/v1/lists/{id}/members
curl -X POST 'https://api.iresendly.com/marketing/v1/lists/{id}/members' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "action": "add",
  "external_ids": [
    "cus_1042",
    "cus_1043"
  ]
}'
Response
{
  "object": "list_members",
  "list_id": "6736a1c4c2a4e51d2f0b7c0a",
  "action": "add",
  "requested": 2,
  "changed": 2,
  "not_found": []
}

List tags

GET/marketing/v1/tagslists:read

Every tag with how many contacts have it.

GET/marketing/v1/tags
curl -X GET 'https://api.iresendly.com/marketing/v1/tags' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "has_more": false,
  "data": [
    {
      "object": "tag",
      "id": "6736a0a1c2a4e51d2f0b7b90",
      "name": "VIP",
      "contact_count": 128,
      "created_at": "2026-11-14T10:00:00.000Z"
    }
  ]
}

List segments

GET/marketing/v1/segmentslists:read

Segments are rules kept in iResendly, so the API reads them but doesn't change them. Send your own segments as lists.

GET/marketing/v1/segments
curl -X GET 'https://api.iresendly.com/marketing/v1/segments' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "has_more": false,
  "data": [
    {
      "object": "segment",
      "id": "seg_71",
      "name": "Opened in the last 30 days",
      "description": null,
      "contact_count": 940,
      "created_at": "2026-10-01T09:00:00.000Z"
    }
  ]
}

Import contacts in the background

POST/marketing/v1/importscontacts:write

Up to 10,000 contacts, taken in by iResendly in the background with the same rules as a single contact. Check progress with GET /imports/{id}. With list and replace_list_members, the list ends up with exactly these contacts: how to keep one of your segments in step.

Body
  • contactsobject[]required

    The contacts, each like a single contact (1–10,000).

  • liststring

    A list id or key:<your key>. Every imported contact is added to it.

  • replace_list_membersboolean

    With list: contacts in the list but not in this import leave it (they stay in your contacts). Only for lists created through the API.

POST/marketing/v1/imports
curl -X POST 'https://api.iresendly.com/marketing/v1/imports' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "list": "key:segment_vip",
  "replace_list_members": true,
  "contacts": [
    {
      "email": "jane@example.com",
      "external_id": "cus_1042"
    }
  ]
}'
Response
{
  "object": "import",
  "id": "4b8e0f2a-…",
  "status": "queued",
  "total": 1,
  "processed": 0,
  "created": 0,
  "updated": 0,
  "skipped": 0,
  "list_id": "6736a1c4c2a4e51d2f0b7c0a",
  "replace_list_members": true,
  "removed_from_list": 0,
  "skipped_rows": [],
  "error": null,
  "created_at": "2026-11-14T10:15:00.000Z",
  "completed_at": null
}

Get an import

GET/marketing/v1/imports/{id}contacts:read

Progress and results. status is queued, running, completed or failed. The first 100 skipped rows are listed with their reason. Imports are kept for 30 days.

Path parameters
  • idstringrequired

    The import id.

GET/marketing/v1/imports/{id}
curl -X GET 'https://api.iresendly.com/marketing/v1/imports/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "import",
  "id": "4b8e0f2a-…",
  "status": "completed",
  "total": 1,
  "processed": 1,
  "created": 1,
  "updated": 0,
  "skipped": 0,
  "list_id": "6736a1c4c2a4e51d2f0b7c0a",
  "replace_list_members": true,
  "removed_from_list": 4,
  "skipped_rows": [],
  "error": null,
  "created_at": "2026-11-14T10:15:00.000Z",
  "completed_at": "2026-11-14T10:15:04.000Z"
}

Send an event

POST/marketing/v1/eventsevents:write

Something happened in your store or app, and the account's automations should hear about it. The contact is added or updated with the same rules as POST /contacts, then the event runs the matching automation triggers. Each id is taken once: sending it again answers duplicate: true and does nothing.

Body
  • eventstringrequired

    order.placed, order.refunded, cart.updated, checkout.completed, form.submitted, download.completed, webinar.registered, event.scheduled, course.completed or subscription.renewing.

  • idstringrequired

    Your id for this event, such as the order or cart id plus what happened. Unique per account for 30 days.

  • emailstringrequired

    Who it happened to.

  • external_idstring

    Your id for the person (as on contacts).

  • first_namestring

    First name.

  • last_namestring

    Last name.

  • subscribedboolean

    false adds a new contact unsubscribed, and no automation starts. Never re-subscribes anyone.

  • tagsstring[]

    Tag names to add to the contact.

  • list_keysstring[]

    Lists to add the contact to, by key.

  • occurred_atstring

    When it happened (ISO 8601). Defaults to now.

  • orderobject

    order.placed and order.refunded: { id, total, currency, items: [{ title, quantity, price, product_id, variant_id, sku }] }. Orders update the contact's order count, total spent and last order, and start purchase automations.

  • refundobject

    order.refunded: { amount, full }. A full refund takes the order off the count and stops that order's follow-ups. A refund never adds a contact.

  • cartobject

    cart.updated: { id, total, currency, recover_url, items }. Starts abandoned-cart automations if no order follows; checkout.completed or order.placed closes the cart.

  • detailsobject

    event.scheduled: { title, starts_at } for reminder automations. Optional title on the other events.

POST/marketing/v1/events
curl -X POST 'https://api.iresendly.com/marketing/v1/events' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "event": "order.placed",
  "id": "order-1042-placed",
  "email": "jane@example.com",
  "external_id": "cus_1042",
  "order": {
    "id": "1042",
    "total": 49.5,
    "currency": "USD",
    "items": [
      {
        "title": "Mango ice",
        "quantity": 2,
        "price": 24.75,
        "product_id": "p_88"
      }
    ]
  }
}'
Response
{
  "object": "event",
  "id": "order-1042-placed",
  "event": "order.placed",
  "duplicate": false,
  "contact_id": "6736a1f0c2a4e51d2f0b7c11",
  "enrolled": 1
}

Add a webhook endpoint

POST/marketing/v1/webhookswebhooks:manage

Where iResendly sends contact.unsubscribed, contact.bounced and contact.complained events. Up to 5 endpoints per account. The answer includes the signing_secret for checking signatures.

Body
  • endpointstringrequired

    Your https address.

  • eventsstring[]required

    The events to send.

POST/marketing/v1/webhooks
curl -X POST 'https://api.iresendly.com/marketing/v1/webhooks' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "endpoint": "https://store.example.com/webhooks/iresendly",
  "events": [
    "contact.unsubscribed",
    "contact.bounced",
    "contact.complained"
  ]
}'
Response
{
  "object": "webhook",
  "id": "6736b2e0c2a4e51d2f0b7d01",
  "endpoint": "https://store.example.com/webhooks/iresendly",
  "events": [
    "contact.unsubscribed",
    "contact.bounced",
    "contact.complained"
  ],
  "status": "enabled",
  "disabled_reason": null,
  "created_at": "2026-11-14T11:00:00.000Z",
  "signing_secret": "whsec_…"
}

List webhook endpoints

GET/marketing/v1/webhookswebhooks:manage

Every endpoint on the account.

GET/marketing/v1/webhooks
curl -X GET 'https://api.iresendly.com/marketing/v1/webhooks' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "list",
  "has_more": false,
  "data": [
    {
      "object": "webhook",
      "id": "6736b2e0c2a4e51d2f0b7d01",
      "endpoint": "https://store.example.com/webhooks/iresendly",
      "events": [
        "contact.unsubscribed"
      ],
      "status": "enabled",
      "disabled_reason": null,
      "created_at": "2026-11-14T11:00:00.000Z"
    }
  ]
}

Get a webhook endpoint

GET/marketing/v1/webhooks/{id}webhooks:manage

One endpoint, with its signing secret.

Path parameters
  • idstringrequired

    The webhook id.

GET/marketing/v1/webhooks/{id}
curl -X GET 'https://api.iresendly.com/marketing/v1/webhooks/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "webhook",
  "id": "6736b2e0c2a4e51d2f0b7d01",
  "endpoint": "https://store.example.com/webhooks/iresendly",
  "events": [
    "contact.unsubscribed"
  ],
  "status": "enabled",
  "disabled_reason": null,
  "created_at": "2026-11-14T11:00:00.000Z",
  "signing_secret": "whsec_…"
}

Update a webhook endpoint

PATCH/marketing/v1/webhooks/{id}webhooks:manage

Change the address or events, or turn it off and on (status: enabled or disabled).

Path parameters
  • idstringrequired

    The webhook id.

Body
  • endpointstring

    New address.

  • eventsstring[]

    New events.

  • statusstring

    enabled or disabled.

PATCH/marketing/v1/webhooks/{id}
curl -X PATCH 'https://api.iresendly.com/marketing/v1/webhooks/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{
  "status": "disabled"
}'
Response
{
  "object": "webhook",
  "id": "6736b2e0c2a4e51d2f0b7d01",
  "endpoint": "https://store.example.com/webhooks/iresendly",
  "events": [
    "contact.unsubscribed"
  ],
  "status": "disabled",
  "disabled_reason": "Disabled manually",
  "created_at": "2026-11-14T11:00:00.000Z"
}

Delete a webhook endpoint

DELETE/marketing/v1/webhooks/{id}webhooks:manage

Stops all events to it straight away.

Path parameters
  • idstringrequired

    The webhook id.

DELETE/marketing/v1/webhooks/{id}
curl -X DELETE 'https://api.iresendly.com/marketing/v1/webhooks/{id}' \
  -H 'Authorization: Bearer irm_xxxxxxxxx'
Response
{
  "object": "webhook",
  "id": "6736b2e0c2a4e51d2f0b7d01",
  "deleted": true
}
Still stuck? Write to us and we'll reply by email.Contact ussupport@iresendly.com