Resend

Name: Resend API
Brand: Resend
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail Deliverybearer69 EndpointsREST

For Agents

Programmatically send an email, retrieve a list of emails. Covers 69 operations with bearer authentication.

Use for: I need to send an email, I want to a list of emails, Search for a single email, Find all a single email

Quickstart

Get started with Resend in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send an email"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Resend API.

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.

GET STARTED

Start building with Resend API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Resend API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'send an email', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

69 endpoints — resend is the email platform for developers.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Resend bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'send an email') and Jentic returns the matching Resend operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Resend integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Resend API through Jentic.

What authentication does the Resend use?

The Resend uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.