apicheats.dev Cheat sheet Raw .md
POST

Try POST /inboxes/{inbox_id}/threads/{thread_id}/emails/{email_id}/forward — Resend API

Resend playground

Forward a thread email

Credentials

Kept in this tab only. Requests go through apicheats.dev's same-origin proxy straight to api.resend.com; the proxy stores and logs nothing about them.

Headers

Path

Body application/json

8 body fields
  • to · required · string — Recipient email address. For multiple addresses, send as an array of strings. Must name at least one address. `to`, `cc` and `bcc` combined cannot exceed 50 recipients. Each address is `[email protected]` or `Name <[email protected]>`. An address that is not valid returns a 422.
  • cc · optional · string — CC recipient email address. For multiple addresses, send as an array of strings. Counts toward the 50-recipient limit. Each address is `[email protected]` or `Name <[email protected]>`. An address that is not valid returns a 422.
  • bcc · optional · string — BCC recipient email address. For multiple addresses, send as an array of strings. Counts toward the 50-recipient limit. Each address is `[email protected]` or `Name <[email protected]>`. An address that is not valid returns a 422.
  • html · optional · string — An HTML note sent above the quoted original.
  • text · optional · string — A plain-text note sent above the quoted original.
  • subject · optional · string — The subject of the forward. Cannot be only whitespace or contain a line break. When omitted, the thread subject is used, prefixed with `Fwd:` if it does not already start with it.
  • attachments · optional · object[] — Files to attach, as on `POST /emails`. Each one needs `content` or `path`. They share one limit with the attachments of the original message, which the forward also sends. Together they can have at most 25 MB of `content`. A `path` file does not count toward the 25 MB, because it is fetched when the email is sent. An empty file, a blocked file type, a `path` that does not start with `http` or that starts with `http://localhost:`, or a `content_type` that is not a valid MIME type returns a 422. Other `path` problems fail the email when it is sent, not the request.
  • headers · optional · object — Custom headers to add to the email. The `In-Reply-To`, `References` and `Reply-To` headers are set by Resend and cannot be set here. Sending one of them, in any letter case, returns a 422. Header names cannot be empty, and names and values cannot contain line breaks or null characters, or the request returns a 422. `null` means no custom headers.