The Resend API is built on REST principles. We enforce HTTPS in every request to improve data security, integrity, and privacy. The API does not support HTTP.
All requests contain the following base URL:
To authenticate you need to add an Authorization header with the contents of the header being
Bearer re_123456789 where
re_123456789 is your API Key.
Authorization: Bearer re_123456789
Resend uses standard HTTP codes to indicate the success or failure of your requests.
2xx HTTP codes correspond to success,
4xx codes are for user-related failures, and
5xx codes are for infrastructure issues.
|Check that the parameters were correct.|
|The API key used was missing.|
|The API key used was invalid.|
|The resource was not found.|
|The rate limit was exceeded.|
|Indicates an error with Resend servers.|
The response headers describe your current rate limit following every request in conformance with the IETF standard:
|Maximum number of requests allowed within a window.|
|How many requests you have left within the current window.|
|How many seconds until the limits are reset.|
|How many seconds you should wait before making a follow-up request.|
The maximum number of requests that users can send is 10 requests per second.
After that, you’ll hit the rate limit and receive a
429 response error code.
To prevent this, we recommend reducing the rate at which you request the API. This can be done by introducing a queue mechanism or reducing the number of concurrent requests per second. If you have specific requirements, contact support to request a rate increase.
Was this page helpful?