> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Resend

> Connect a sending-only or full-access API key for authorized email work.

Create an API key in Resend's **API Keys** page. Prefer **Sending access**,
restricted to the intended domain when possible, for a mail-only workflow.
Use Full access only when the agent needs other supported account operations.

An Administrator opens **Connectors → Connect → Resend**, enters a label and the
key into the secure form, and saves. Nuphos probes its permission level and
stores it encrypted. A sending-only key is not an invalid key merely because
it cannot list domains.

## Sending email

Select the binding and give the exact recipients, sender, subject and content.
The sender must be allowed by the key and your verified domain configuration.
Sending is an external action that cannot be recalled; approve that specific
message rather than granting an open-ended recipient list.

For setup verification, inspect the recorded permission and domain information
available to your key. Send a test only when you have explicitly requested it
and named the recipient. An API accepting a send is not proof of final delivery.

## Troubleshooting and revocation

Check the sender domain, key permission, recipient and delivery status before
retrying a send; duplicate retries can send duplicate mail. Remove the binding
in Nuphos and revoke the key in Resend when retiring it. Previously sent mail
and provider logs remain.

See [Resend key permissions](https://resend.com/changelog/new-api-key-permissions).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.