Skip to main content

Base URL

The Unosend 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:

Authentication

To authenticate you need to add an Authorization header with the contents of the header being Bearer un_xxxxxxxxxx where un_xxxxxxxxxx is your API Key.
Keep your API key secure and never expose it in client-side code.

Response codes

Unosend uses standard HTTP codes to indicate the success or failure of your requests. In general, 2xx HTTP codes correspond to success, 4xx codes are for user-related failures, and 5xx codes are for infrastructure issues.

Rate limit

The API has a rate limit of 100 requests per second. If you exceed this limit, you’ll receive a 429 response. Rate limit headers are included in all responses:

Pagination

List endpoints support pagination using limit and offset query parameters:

FAQ

Unosend API keys start with un_ prefix for easy identification.
No, API requests should only be made from your server to keep your API key secure. Never expose your API key in client-side code.
The maximum total email size (headers + body + inline images + attachments) is 15 MB.