Resend
Resend — free tier with API key
Resend exposes a free-tier JSON API. Register for an API key if required; we verified a public or demo endpoint.
GET https://resend.com/api/v1
{
"type": "not_authenticated",
"message": "The user does not have an active session or is not authenticated"
}curl "https://resend.com/api/v1"const res = await fetch("https://resend.com/api/v1");
const data = await res.json();
console.log(data);import requests
res = requests.get("https://resend.com/api/v1")
print(res.json())THIS API IS DEAD — NOTHING TO RUN
/api/v1PROBEDResend — free tier with API key
/apiApi — documented GET route.
/api/1Api details by ID (example: 1).
/api?limit=10Api — documented GET route.
/api/search?q=testSearch by query parameters.
/emailsRetrieve a list of emails
We probe a documented GET and expect 2xx JSON — full uptime and health score. Export includes every documented route below.
Stable. No schema drift observed since monitoring began — the response shape has not changed under our checks.
Resend: common questions
Is Resend free to use?
Yes — Resend is a free social & work API. Free tier: Free tier — API key required. Whether the free tier allows commercial use is unclear — check the provider docs.
Does Resend need an API key?
Yes — Resend needs a free API key, which you pass on each request. Rate limits: Unpublished.
Can I call Resend from the browser?
Not directly — Resend doesn't send browser-friendly CORS headers, so call it from a server or proxy instead. Copy the curl or Python snippet on this page to get started.
Is Resend up right now?
As of our last scheduled check, Resend is dead. We re-probe it every sweep — the status badge and uptime chart above always show the latest.