POST
/api-keys
Resend APICreate a new API key
- Base URL
- https://api.resend.com
- Auth
- Authorization: Bearer <RESEND_API_KEY>
- Last verified
- 2026-09-03 · upstream hash matched
Actions
Agents: curl -H "Accept: text/markdown" this URL
→ 229 tokens · Vary: Accept
→ 229 tokens · Vary: Accept
Critical gotchas
All requests must include a User-Agent header (e.g. User-Agent: my-app/1.0) or the API returns HTTP 403.
The to field is an array of strings, even when sending to a single recipient.
cURL
curl -X POST 'https://api.resend.com/api-keys' \ -H "Authorization: Bearer $RESEND_API_KEY" \ -H 'User-Agent: my-app/1.0' \ -H 'Content-Type: application/json' \ -d '{ "name": "string", "permission": "full_access", "domain_id": "string"}'Get a free Resend API key → sponsored
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| name | body | string | Yes | The API key name. |
| permission | body | string | No | The API key can have full access to Resend’s API or be only restricted to send emails. * full_access - Can create, delete, get, and update any resource. * sending_access - Can only send emails. |
| domain_id | body | string | No | Restrict an API key to send emails only from a specific domain. Only used when the permission is sending_access. |
Response 200 OK
{
"id": "string",
"token": "string"
}