Resend
Email API for developers to send transactional and marketing email
Resend ships SSO and enters the enterprise conversation as its product surface broadens.
◆Recent moves
- 1d agoView source ↗
List Clicked Links API
- 2d ago
Update Segment API
Segments can now be renamed via the API, CLI, and SDKs — a completeness fix that brings segment management in line with other Resend resources that already support rename operations. Fits the ongoing pattern of API surface parity work.
View source ↗ - 6d ago
New Table Component
A native table component now available in Broadcasts and Templates extends Resend's email composition surface — useful for data-heavy transactional emails like invoices or summaries. Adds visual flexibility without requiring custom HTML.
View source ↗ - 8d ago
Vercel v0 Integration
Vercel v0 now has a Resend integration, letting developers wire up email from within the v0 UI without switching contexts. A distribution move: Resend embedding into a popular scaffolding tool reaches developers before they've decided on an email provider.
View source ↗ - 13d ago
Link Checker
Link Checker surfaces broken, missing, or placeholder links before a Broadcast sends or a Template publishes — a pre-send safety net that reduces the risk of embarrassing delivery. Part of the broader push to make Resend viable for high-volume, non-developer-driven email operations.
View source ↗ - 15d ago
Single Sign-On
⚡ SPARKSSO lands on Resend, letting teams authenticate through an existing identity provider. This is the most directional move in the recent batch: SSO is not a developer request, it is an enterprise procurement requirement. It changes who can buy Resend at scale.
View source ↗