Retrieve an email (Resend dialect)
Drop-in for Resend's GET /emails/{id}. Looks the email up inside the authenticated project only.
The key must hold emails:read, NOT emails:send: this is the one compat route that reads. A pk_ send-only key is refused with 403.
The mapping is lossy by design — see last_event and the always-null fields. For the real delivery status and engagement use GET /api/emails/{id}.
Authorization
ApiKeyAuth API key authentication. Use a sk_* (FULL) or pk_* (SENDING_ONLY) key as the bearer token. Public keys (pk_*) are restricted to the email-send endpoints and the self-serve list subscribe/unsubscribe pair; every other endpoint — event tracking included — answers 403 for them. In scope terms (used by /api/v1/* operations): FULL keys hold every scope; SENDING_ONLY keys hold only emails:send.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/compat/resend/emails/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"object": "email",
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"to": [
"string"
],
"from": "string",
"created_at": "2019-08-24T14:15:22Z",
"subject": "string",
"html": "string",
"text": null,
"bcc": null,
"cc": null,
"reply_to": null,
"last_event": "queued"
}{
"statusCode": 0,
"message": "string",
"name": "string"
}{
"statusCode": 0,
"message": "string",
"name": "string"
}{
"statusCode": 0,
"message": "string",
"name": "string"
}{
"statusCode": 0,
"message": "string",
"name": "string"
}{
"statusCode": 0,
"message": "string",
"name": "string"
}