Skip to content
Changelog

Report a bug

Resend integration: operations for AI agents

Resend connects to Type.com as an integration. This page lists the 142 operations documented for Claude and Codex in Type.com: 62 read, 37 write, 43 destructive.

About Resend

Resend vendor API references, subject to account permissions.

Categories: Email & Messaging

How to connect Resend to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

142 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

142 operations listed.

Emails

  • Read

    Retrieve a list of emails

    Retrieve a list of emails

    GET /emails

  • Read

    Retrieve a single email

    Retrieve a single email

    GET /emails/{email_id}

  • Read

    Retrieve a list of attachments for a sent email

    Retrieve a list of attachments for a sent email

    GET /emails/{email_id}/attachments

  • Read

    Retrieve a single attachment for a sent email

    Retrieve a single attachment for a sent email

    GET /emails/{email_id}/attachments/{attachment_id}

  • Read

    Retrieve account-level email metrics

    Retrieve account-level email metrics

    GET /emails/metrics

  • Write

    Send an email

    Send an email

    POST /emails

  • Write

    Update a single email

    Update a single email

    PATCH /emails/{email_id}

  • Write

    Create a shareable link for a sent or received email.

    Create a shareable link for a sent or received email.

    POST /emails/{email_id}/share

  • Write

    Trigger up to 100 batch emails at once.

    Trigger up to 100 batch emails at once.

    POST /emails/batch

  • Destructive

    Cancel the schedule of the e-mail.

    Cancel the schedule of the e-mail.

    POST /emails/{email_id}/cancel

Receiving Emails

  • Read

    Retrieve a list of received emails

    Retrieve a list of received emails

    GET /emails/receiving

  • Read

    Retrieve a single received email

    Retrieve a single received email

    GET /emails/receiving/{email_id}

  • Read

    Retrieve a list of attachments for a received email

    Retrieve a list of attachments for a received email

    GET /emails/receiving/{email_id}/attachments

  • Read

    Retrieve a single attachment for a received email

    Retrieve a single attachment for a received email

    GET /emails/receiving/{email_id}/attachments/{attachment_id}

Domains

  • Read

    Retrieve a list of domains

    Retrieve a list of domains

    GET /domains

  • Read

    Retrieve a single domain

    Retrieve a single domain

    GET /domains/{domain_id}

  • Read

    Retrieve a domain claim

    Retrieve the latest claim for the placeholder domain created by the claim.

    GET /domains/{domain_id}/claim

  • Write

    Create a new domain

    Create a new domain

    POST /domains

  • Write

    Verify an existing domain

    Triggers verification of the domain's DNS records including DKIM, SPF, and the tracking CNAME (if a tracking subdomain is configured).

    POST /domains/{domain_id}/verify

  • Destructive

    Update an existing domain

    Update an existing domain

    PATCH /domains/{domain_id}

  • Destructive

    Remove an existing domain

    Remove an existing domain

    DELETE /domains/{domain_id}

  • Destructive

    Claim a domain

    Start a claim for a domain that another Resend account has already verified. The domain is recreated under your account with fresh DKIM keys, so the previous account's DNS records cannot be reused. Returns a TXT record to add to your DNS to prove ownership. Uses the same request body as creating a domain.

    POST /domains/claim

  • Destructive

    Verify a domain claim

    Trigger asynchronous DNS verification and ownership transfer for a domain claim. The claim stays `pending` while verification runs; poll the retrieve endpoint for status. Once `completed`, the transferred domain has new DKIM records that must be added to DNS and verified via the standard domain verify endpoint.

    POST /domains/{domain_id}/claim/verify

API Keys

  • Read

    Retrieve a list of API keys

    Retrieve a list of API keys

    GET /api-keys

  • Write

    Create a new API key

    Create a new API key

    POST /api-keys

  • Write

    Update an existing API key

    Update an existing API key

    PATCH /api-keys/{api_key_id}

  • Destructive

    Remove an existing API key

    Remove an existing API key

    DELETE /api-keys/{api_key_id}

OAuth

  • Read

    Retrieve a list of OAuth grants

    Retrieve a list of OAuth grants

    GET /oauth/grants

  • Destructive

    Revoke an OAuth grant

    Revoke an OAuth grant

    DELETE /oauth/grants/{oauth_grant_id}

Templates

  • Read

    Retrieve a list of templates

    Retrieve a list of templates

    GET /templates

  • Read

    Retrieve a single template

    Retrieve a single template

    GET /templates/{id}

  • Write

    Create a template

    Create a template

    POST /templates

  • Write

    Update an existing template

    Update an existing template

    PATCH /templates/{id}

  • Write

    Publish a template

    Publish a template

    POST /templates/{id}/publish

  • Write

    Duplicate a template

    Duplicate a template

    POST /templates/{id}/duplicate

  • Destructive

    Remove an existing template

    Remove an existing template

    DELETE /templates/{id}

Audiences

  • Read

    Retrieve a list of audiences (deprecated)

    Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.

    GET /audiences

  • Read

    Retrieve a single audience (deprecated)

    Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.

    GET /audiences/{id}

  • Write

    Create a list of contacts (deprecated)

    Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.

    POST /audiences

  • Destructive

    Remove an existing audience (deprecated)

    Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.

    DELETE /audiences/{id}

Contacts

  • Read

    Retrieve a list of contacts

    Retrieve a list of contacts

    GET /contacts

  • Read

    Retrieve a list of contact imports

    Retrieve a list of contact imports

    GET /contacts/imports

  • Read

    Retrieve a single contact import

    Retrieve a single contact import

    GET /contacts/imports/{id}

  • Read

    Retrieve a single contact by ID or email

    Retrieve a single contact by ID or email

    GET /contacts/{id}

  • Read

    Retrieve a list of segments for a contact

    Retrieve a list of segments for a contact

    GET /contacts/{contact_id}/segments

  • Read

    Retrieve topics for a contact

    Retrieve topics for a contact

    GET /contacts/{contact_id}/topics

  • Write

    Create a contact import

    Create a contact import

    POST /contacts/imports

  • Write

    Add a contact to a segment

    Add a contact to a segment

    POST /contacts/{contact_id}/segments/{segment_id}

  • Destructive

    Create a new contact

    Create a new contact

    POST /contacts

  • Destructive

    Update a single contact by ID or email

    Update a single contact by ID or email

    PATCH /contacts/{id}

  • Destructive

    Remove an existing contact by ID or email

    Remove an existing contact by ID or email

    DELETE /contacts/{id}

  • Destructive

    Remove a contact from a segment

    Remove a contact from a segment

    DELETE /contacts/{contact_id}/segments/{segment_id}

  • Destructive

    Update topics for a contact

    Update topics for a contact

    PATCH /contacts/{contact_id}/topics

Broadcasts

  • Read

    Retrieve a list of broadcasts

    Retrieve a list of broadcasts

    GET /broadcasts

  • Read

    Retrieve a single broadcast

    Retrieve a single broadcast

    GET /broadcasts/{id}

  • Read

    Retrieve broadcast recipients

    Retrieve the recipients of a broadcast for a given event type, such as who opened, clicked, or bounced.

    GET /broadcasts/{id}/recipients

  • Write

    Create a broadcast

    Create a broadcast

    POST /broadcasts

  • Write

    Update an existing broadcast

    Update an existing broadcast

    PATCH /broadcasts/{id}

  • Write

    Send or schedule a broadcast

    Send or schedule a broadcast

    POST /broadcasts/{id}/send

  • Write

    Duplicate a broadcast

    Creates a new draft broadcast with the same segment, topic, sender, subject, reply-to, preview text, and content as the source. The copy is named after the source with " (copy)" appended, truncated to 70 characters.

    POST /broadcasts/{id}/duplicate

  • Destructive

    Remove an existing broadcast that is in the draft status

    Remove an existing broadcast that is in the draft status

    DELETE /broadcasts/{id}

  • Destructive

    Cancel a broadcast

    Cancels a broadcast that is queued or scheduled. Canceling a queued broadcast stops it mid-send; emails already sent are not affected, but no further emails will go out.

    POST /broadcasts/{id}/cancel

Webhooks

  • Read

    Retrieve a list of webhooks

    Retrieve a list of webhooks

    GET /webhooks

  • Read

    Retrieve a single webhook

    Retrieve a single webhook

    GET /webhooks/{webhook_id}

  • Read

    Retrieve a list of webhook events

    Retrieve a list of webhook events

    GET /webhooks/{webhook_id}/events

  • Read

    Retrieve a single webhook event

    Retrieve a single webhook event

    GET /webhooks/{webhook_id}/events/{event_id}

  • Read

    Retrieve a list of webhook event attempts

    Retrieve a list of webhook event attempts

    GET /webhooks/{webhook_id}/events/{event_id}/attempts

  • Write

    Create a new webhook

    Create a new webhook

    POST /webhooks

  • Write

    Replay a webhook event

    Queues one more delivery of the event to the webhook. The event must be retrievable through the get event endpoint and the webhook must be enabled; a disabled webhook returns a 422 validation_error. A manual replay does not schedule automatic retries.

    POST /webhooks/{webhook_id}/events/{event_id}/replay

  • Destructive

    Update an existing webhook

    Update an existing webhook

    PATCH /webhooks/{webhook_id}

  • Destructive

    Remove an existing webhook

    Remove an existing webhook

    DELETE /webhooks/{webhook_id}

  • Destructive

    Rotate a webhook signing secret

    Generates a new signing secret for the webhook and returns it. Payloads delivered after the rotation are signed with the new secret. The previous secret keeps verifying payloads for 24 hours, so both secrets are accepted during that window. A webhook that does not exist or was removed returns a 404 not_found.

    POST /webhooks/{webhook_id}/signing-secret/rotate

Segments

  • Read

    Retrieve a list of segments

    Retrieve a list of segments

    GET /segments

  • Read

    Retrieve a single segment

    Retrieve a single segment

    GET /segments/{id}

  • Read

    Retrieve a list of contacts in a segment

    Retrieve a list of contacts in a segment

    GET /segments/{id}/contacts

  • Write

    Create a new segment

    Create a new segment

    POST /segments

  • Write

    Update an existing segment

    Update an existing segment

    PATCH /segments/{id}

  • Destructive

    Remove an existing segment

    Remove an existing segment

    DELETE /segments/{id}

Topics

  • Read

    Retrieve a list of topics

    Retrieve a list of topics

    GET /topics

  • Read

    Retrieve a single topic

    Retrieve a single topic

    GET /topics/{id}

  • Write

    Create a new topic

    Create a new topic

    POST /topics

  • Write

    Update an existing topic

    Update an existing topic

    PATCH /topics/{id}

  • Destructive

    Remove an existing topic

    Remove an existing topic

    DELETE /topics/{id}

Contact Properties

  • Read

    Retrieve a list of contact properties

    Retrieve a list of contact properties

    GET /contact-properties

  • Read

    Retrieve a single contact property

    Retrieve a single contact property

    GET /contact-properties/{id}

  • Write

    Create a new contact property

    Create a new contact property

    POST /contact-properties

  • Write

    Update an existing contact property

    Update an existing contact property

    PATCH /contact-properties/{id}

  • Destructive

    Remove an existing contact property

    Remove an existing contact property

    DELETE /contact-properties/{id}

Logs

  • Read

    Retrieve a list of logs

    Retrieve a list of logs

    GET /logs

  • Read

    Retrieve a single log

    Retrieve a single log

    GET /logs/{log_id}

Automations

  • Read

    Retrieve a list of automations

    Retrieve a list of automations

    GET /automations

  • Read

    Retrieve a single automation

    Retrieve a single automation

    GET /automations/{automation_id}

  • Read

    Retrieve a list of automation runs

    Retrieve a list of automation runs

    GET /automations/{automation_id}/runs

  • Read

    Retrieve a single automation run

    Retrieve a single automation run

    GET /automations/{automation_id}/runs/{run_id}

  • Write

    Duplicate an automation

    Duplicate an automation

    POST /automations/{automation_id}/duplicate

  • Destructive

    Create an automation

    Create an automation

    POST /automations

  • Destructive

    Update an automation

    Update an automation

    PATCH /automations/{automation_id}

  • Destructive

    Delete an automation

    Delete an automation

    DELETE /automations/{automation_id}

  • Destructive

    Stop an automation

    Stop an automation

    POST /automations/{automation_id}/stop

Events

  • Read

    Retrieve a list of events

    Retrieve a list of events

    GET /events

  • Read

    Retrieve a single event

    Retrieve a single event

    GET /events/{identifier}

  • Write

    Create an event

    Create an event

    POST /events

  • Destructive

    Send an event

    Send an event

    POST /events/send

  • Destructive

    Update an event

    Update an event

    PATCH /events/{identifier}

  • Destructive

    Delete an event

    Delete an event

    DELETE /events/{identifier}

Suppressions

  • Read

    Retrieve a list of suppressions

    Retrieve a list of suppressions

    GET /suppressions

  • Read

    Retrieve a single suppression by ID or email

    Retrieve a single suppression by ID or email

    GET /suppressions/{suppression}

  • Destructive

    Create a suppression

    Create a suppression

    POST /suppressions

  • Destructive

    Add up to 100 suppressions at once

    Add up to 100 suppressions at once

    POST /suppressions/batch/add

  • Destructive

    Remove up to 100 suppressions at once

    Remove up to 100 suppressions at once

    POST /suppressions/batch/remove

  • Destructive

    Remove a single suppression by ID or email

    Remove a single suppression by ID or email

    DELETE /suppressions/{suppression}

Usage

  • Read

    Retrieve account usage

    Retrieve your account's current usage and plan limits.

    GET /usage

Inboxes

  • Read

    Retrieve a list of inboxes

    Returns the inboxes of the team, newest first. The list items carry fewer fields than a single inbox. Retrieve an inbox to get all its fields. The `after` and `before` cursors take an inbox ID, and only one of them can be passed, or the request returns a 422. A value that is not a UUID returns a 422, and an unknown ID returns a 404.

    GET /inboxes

  • Read

    Retrieve a single inbox by ID or email address

    Retrieve a single inbox by ID or email address

    GET /inboxes/{inbox_id}

  • Read

    Retrieve the agent settings for an inbox

    Returns the agent settings of the inbox. An inbox without a configured agent returns empty settings: `instructions` and `tone` are null and `actions` is an empty array.

    GET /inboxes/{inbox_id}/agent

  • Read

    Retrieve a list of inbox labels

    Returns every label on the inbox, oldest first. The list is not paginated.

    GET /inboxes/{inbox_id}/labels

  • Read

    Retrieve a list of inbox threads

    Returns the threads in an inbox, most recently active first. A thread is a conversation made up of one or more emails. The `after` and `before` cursors take a thread ID, and only one of them can be passed. A cursor that is not a UUID, such as a date, returns a 422 validation_error. A cursor thread that is not in the selected folders returns a 404. To find threads by text, sender, recipient, attachment, or date, use the search threads endpoint.

    GET /inboxes/{inbox_id}/threads

  • Read

    Search the threads of an inbox

    Finds threads by the text of their emails, who sent or received them, whether they have attachments, and their dates. Results are ordered by latest activity, newest first, and paginate like the list threads endpoint, so a cursor that is not a thread ID returns a 422. Search can be up to about a minute behind new emails. Different parameters combine, so a thread must match all of them. `folders`, `labels`, and `read` apply to the thread. `query`, `from`, `to`, `cc`, `bcc`, `has_attachment`, `start_date`, and `end_date` must all match the same email in the thread. When any of these email filters is set, the matching email must itself be in one of `folders`. For `sent`, that means an email the inbox sent. When more than 10,000 threads match, search covers the 10,000 with the newest matching email.

    GET /inboxes/{inbox_id}/threads/search

  • Read

    Retrieve a single inbox thread

    Returns the thread summary. The emails in the thread are listed with the list thread emails endpoint.

    GET /inboxes/{inbox_id}/threads/{thread_id}

  • Read

    Retrieve a list of thread emails

    Returns the messages of a thread, oldest first. Pass the `id` of the last message as `after` to get the next, newer page. Pass the `id` of the first message as `before` to get the previous, older page. Passing both `after` and `before`, or a cursor that is not a UUID, returns a 422. A cursor that is not a message of the thread returns a 404.

    GET /inboxes/{inbox_id}/threads/{thread_id}/emails

  • Read

    Retrieve a single thread email

    Retrieve a single thread email

    GET /inboxes/{inbox_id}/threads/{thread_id}/emails/{email_id}

  • Read

    Retrieve a list of drafts

    Returns the unsent drafts on the inbox, most recently updated first. The `after` and `before` cursors take a Draft ID from the current page, and only one of them can be passed. A cursor that is not a UUID, or both cursors together, return a 422. A cursor that is not an unsent draft on this inbox returns a 404.

    GET /inboxes/{inbox_id}/drafts

  • Read

    Retrieve a single draft

    Retrieve a single draft

    GET /inboxes/{inbox_id}/drafts/{draft_id}

  • Write

    Create an inbox

    Creates an inbox that sends and receives email at an address on one of your domains. The domain must belong to the team. Without `forwarding`, the domain must have receiving enabled, with DKIM and SPF verified and the inbound MX record verified or pending. With `forwarding` set to `true`, the domain only needs DKIM and SPF verified for sending, and Resend generates a `receiving_address` on the team inbound domain, and a team without an inbound domain gets a 422. A domain that does not meet these rules returns a 422 validation_error. An address or receiving address that is already in use returns a 409. A team that has reached the inbox limit of its plan returns a 403 validation_error. A blocked account returns a 451.

    POST /inboxes

  • Write

    Create a label on an inbox

    A label is a named, colored tag that belongs to one inbox. An inbox can have at most 100 labels. Label names are unique per inbox, compared without case. A duplicate name or a full inbox returns a 422 validation_error.

    POST /inboxes/{inbox_id}/labels

  • Write

    Update an existing inbox label

    Renames or recolors a label. Omitted fields keep their current value. A new name must not match another label on the inbox, compared without case, or the request returns a 422 validation_error.

    PATCH /inboxes/{inbox_id}/labels/{label_id}

  • Write

    Add labels to an inbox thread

    Applies one or more labels to the thread. Labels already on the thread stay on it. The response lists every label on the thread after the change. A label ID that is not a label of the inbox returns a 404 `Label not found.`, and nothing changes. A thread that does not exist in the inbox returns a 404 `Thread not found.`. To replace the labels of the thread, use the set thread labels endpoint.

    POST /inboxes/{inbox_id}/threads/{thread_id}/labels

  • Write

    Reply to a thread email

    Sends a reply from the inbox address right away, with no stored draft. The `to` recipients come from the message you reply to. For a message the inbox received, the reply goes to its `Reply-To` addresses, or to its sender when it has no `Reply-To`. For a message the inbox sent, the reply goes to that message's `to` recipients. Set `reply_all` to also copy the other recipients of the message. The reply threads under the message through the `In-Reply-To` and `References` headers. When no recipient can be found for the reply, the request returns a 422. The whole email, encoded, can be at most 40 MB, or the request returns a 422.

    POST /inboxes/{inbox_id}/threads/{thread_id}/emails/{email_id}/reply

  • Write

    Forward a thread email

    Forwards a message from the inbox address right away, with no stored draft. The original message is quoted under a forwarded-message banner, below the optional `html` or `text` note. The attachments of the original message are sent with the forward, together with any `attachments` you add. The request returns a 422 when they exceed 25 MB of `content` in total. An original attachment that was sent from a URL (`path`) cannot be forwarded, and the request returns a 422. The whole email, encoded, can be at most 40 MB, or the request returns a 422.

    POST /inboxes/{inbox_id}/threads/{thread_id}/emails/{email_id}/forward

  • Write

    Create a draft

    Creates an unsent draft on the inbox. Omit `thread_id` and `reply_to_email_id` for a draft that starts a new thread. Pass both together for a reply draft in an existing thread. A reply draft without `to` is addressed to the sender of the email it replies to, or to its Reply-To when set. For an email the inbox sent, it defaults to that email's `to` recipients. Send `to: []` to leave it empty. At least one of `to`, `cc`, `bcc`, `subject`, `text`, `html` or `attachments` must be non-empty. The combined recipients of `to`, `cc` and `bcc` cannot exceed 50. Attachments are stored on the draft, so each one needs `content`, `filename` and `content_type`. Returns 201 for a new draft. Only one unsent reply draft can target an email, so a reply draft request for an email that already has one returns 200 with the ID of the existing draft. An unknown `thread_id`, or a `reply_to_email_id` that is not in that thread, returns a 404. That request ignores every other field, except `attachments`, which replaces the attachments of the existing draft when sent. A reply draft created without `subject` stores an empty subject. When it is sent, it takes the thread subject, prefixed with `Re:` when it does not already start with it.

    POST /inboxes/{inbox_id}/drafts

  • Write

    Send a draft

    Sends the draft from the inbox address. A reply draft is sent in its thread. A draft without a thread starts a new thread. The draft must have at least one `to` recipient and `html` or `text`, or the request returns a 422. A standalone draft also needs a non-empty `subject`. A reply draft with an empty `subject` is sent with the thread subject, prefixed with `Re:` when it does not already start with it. A draft that was already sent returns a 409. The request body is optional and takes only `headers`. The whole email, encoded, can be at most 40 MB, or the request returns a 422.

    POST /inboxes/{inbox_id}/drafts/{draft_id}/send

  • Destructive

    Update an existing inbox by ID or email address

    Updates the internal name of the inbox or the name recipients see when mail is sent from it. At least one of `name` or `from_name` is required.

    PATCH /inboxes/{inbox_id}

  • Destructive

    Remove an existing inbox by ID or email address

    Removes the inbox. An inbox that does not exist or was already removed returns a 404 not_found.

    DELETE /inboxes/{inbox_id}

  • Destructive

    Update the agent settings for an inbox

    Updates the agent settings of the inbox. The agent is created when the inbox has none. Omitted fields keep their current value.

    PATCH /inboxes/{inbox_id}/agent

  • Destructive

    Remove an existing inbox label

    Deletes the label and removes it from every thread that carries it.

    DELETE /inboxes/{inbox_id}/labels/{label_id}

  • Destructive

    Update an existing inbox thread

    Marks a thread read or unread, or moves it to a folder. At least one of `read` or `folder` is required. To change the labels of a thread, use the add, set, and remove thread labels endpoints. This endpoint ignores the removed `add_label_ids` and `remove_label_ids` fields, so a body with only those fields returns a 422 validation_error. Moving a thread out of `trash` restores it and clears its deletion deadline. The changes apply in this order: `read`, then `folder`. They are not atomic.

    PATCH /inboxes/{inbox_id}/threads/{thread_id}

  • Destructive

    Remove an existing inbox thread

    Moves the thread to `trash` and schedules it for deletion in 30 days. This is reversible. To restore the thread, update its `folder` to `inbox`, `archive`, or `spam`, which also clears the deletion deadline.

    DELETE /inboxes/{inbox_id}/threads/{thread_id}

  • Destructive

    Set the labels of an inbox thread

    Replaces every label on the thread with the given labels, in one atomic change. Labels on the thread that are not in the list are taken off it. The labels themselves are kept. An empty array takes every label off the thread. The response lists every label on the thread after the change. A label ID that is not a label of the inbox returns a 404 `Label not found.`, and nothing changes. A thread that does not exist in the inbox returns a 404 `Thread not found.`.

    PUT /inboxes/{inbox_id}/threads/{thread_id}/labels

  • Destructive

    Remove a label from an inbox thread

    Takes one label off the thread. The label itself is kept, and stays on every other thread that carries it. To delete the label, use the remove inbox label endpoint. The response lists every label on the thread after the change. A label that is not on the thread returns a 200 with the current labels. A label ID that is not a label of the inbox returns a 404 `Label not found.`. A thread that does not exist in the inbox returns a 404 `Thread not found.`.

    DELETE /inboxes/{inbox_id}/threads/{thread_id}/labels/{label_id}

  • Destructive

    Update an existing draft

    Updates the content of an unsent draft. Omitted fields are left unchanged. Send at least one of `to`, `cc`, `bcc`, `subject`, `text`, `html` or `attachments`. Sending `attachments` replaces every attachment on the draft. A request that sets `text` or `html` replaces the whole body. The body part you omit from that request becomes `null`. The merged draft must still contain at least one non-empty field, and its combined recipients cannot exceed 50. A draft that was already sent, or that changed during the request, returns a 409. The response holds only the Draft ID. Retrieve the draft to read its content.

    PATCH /inboxes/{inbox_id}/drafts/{draft_id}

  • Destructive

    Remove an existing draft

    Discards an unsent draft. A draft that was already sent, or that changed during the request, returns a 409.

    DELETE /inboxes/{inbox_id}/drafts/{draft_id}

See How connections work for access and permissions, or browse all integrations.