Recommendation: Use a Resend SDK for your language. Call the raw
API directly only when no SDK exists for your
stack.
Choosing between the SDK and API
Reach for the SDK unless you have a specific reason not to. It handles authentication, the requiredUser-Agent header, request serialization, typed
responses, and error handling for you. That leaves less boilerplate to get
wrong.
| Resend SDK (recommended) | Raw HTTP API | |
|---|---|---|
| Auth & headers | Handled automatically | Set Authorization and User-Agent manually |
| Types & autocomplete | Built in | None |
| Errors | Structured error objects | Parse status codes and JSON yourself |
| Maintained by | Resend | You |
When to use the raw API directly
Calling the API directly is a good fit when:- There’s no official SDK for your language or runtime.
- You’re making a one-off request and don’t want to add a dependency.
- You’re building your own integration or wrapper.
User-Agent header.
Next steps
Official SDKs
Install the SDK for your language.
Quickstart
Send your first email in minutes.
API Reference
Full HTTP API documentation.
MCP Server
Give your AI agent access to Resend.