canonical: https://jentic.com/apis/resend.com/resend # Resend Resend is the email platform for developers. The API exposes 69 endpoints secured with bearer authentication. ## For AI agents Programmatically send an email, retrieve a list of emails. Covers 69 operations with bearer authentication. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - Send an email - Retrieve a list of emails - Update a single email - Cancel the schedule of the e-mail. - Trigger up to 100 batch emails at once. ## Use cases ### Communications Operations Use the Resend to perform communications operations programmatically. The API provides 69 endpoints covering core functionality including send an email, retrieve a list of emails, retrieve a single email. Example prompt: Call POST /emails to send an email ### Automated Emails Management Automate emails operations by combining multiple Resend endpoints. Agents can retrieve a list of emails and then retrieve a single email in a single workflow. Example prompt: Call GET /emails to retrieve a list of emails, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Resend endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually. Example prompt: Search Jentic for 'send an email', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /emails | Send an email | | GET | /emails | Retrieve a list of emails | | GET | /emails/{email_id} | Retrieve a single email | | PATCH | /emails/{email_id} | Update a single email | | POST | /emails/{email_id}/cancel | Cancel the schedule of the e-mail. | | POST | /emails/batch | Trigger up to 100 batch emails at once. | | GET | /emails/{email_id}/attachments | Retrieve a list of attachments for a sent email | | GET | /emails/{email_id}/attachments/{attachment_id} | Retrieve a single attachment for a sent email | ## Key resources - **Emails** — Start sending emails through the Resend API. - **Domains** — Create and manage domains through the Resend API. - **API Keys** — Create and manage API Keys through the Resend API. - **Audiences** — Deprecated: Use Segments instead. Create and manage Audiences through the Resend API. - **Contacts** — Create and manage Contacts through the Resend API. ## Why Jentic - **Setup:** Wiring Resend by hand means setting its bearer auth on every request, tracking email ids across send, read, update, and cancel calls, and handling batch and attachment endpoints yourself. Through Jentic you install once, import Resend from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Resend puts the email id in the URL path (/emails/{email_id}), so a rule can pin your agent to reading and updating a specific email. You choose the operations it may call, so a state-changing one like cancelling a scheduled email is not included unless you add it. - **Credential handling:** Your Resend token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send an email' or 'cancel a scheduled email', and Jentic returns the matching Resend operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio** — Alternative communications API - **Sendgrid** — Alternative communications API - **Pusher** — Complementary communications API ## FAQ ### What authentication does the Resend use? The Resend uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I send an email with the Resend? Yes. Use the POST /emails endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Resend? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I send an email through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send an email'. Jentic returns the matching Resend operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Resend have? The Resend exposes 69 endpoints covering emails, domains, API keys operations. ### Can I limit what my agent is allowed to do with the Resend API? Yes. Because you run Jentic One yourself, your own rules decide which Resend operations and credentials the agent may use. You can grant it just the calls you want, such as POST /emails to send or GET /emails to read, while leaving out state-changing ones like cancelling a scheduled email at /emails/{email_id}/cancel. Since Resend puts the email id in the URL path, a rule can also pin the agent to reading or updating one specific email rather than every message on the account.