What Resend changed, 10 April 2026 to 30 October 2026
83 operations became 142. None were removed, 0 were newly deprecated, 59 were added, and 0 request fields became required.
Read from resend/resend-openapi at 99ec8d3 and 0b2a456 (version 1.5.1). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Resend's published specification.
Resend publishes its API description in resend/resend-openapi, as resend.yaml and resend.json. This page reads resend.json. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.
Removed from the specification
Nothing was removed in this window. That is a real result, not a gap in the check.
Newly deprecated in this window
A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.
No compared operation (one paired with a baseline operation) gained the deprecated flag in this window.
Deprecated as of the current specification (4)
Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.
- DELETE /audiences/{id}
- GET /audiences
- GET /audiences/{id}
- POST /audiences
Entries without a link were already marked deprecated at 99ec8d3 · 10 April 2026, the baseline compared here.
Resend API questions
Every answer below is computed from the snapshot above, and each links to the Resend specification it was read from.
- Which Resend API endpoints were removed recently?
- None between 10 April 2026 and 30 October 2026, in resend.json in resend/resend-openapi. It went from 83 to 142 operations in that window, and every operation present at the start was still there at the end, at the same URL.
- Source: resend/resend-openapi, the two commits compared
- Which Resend API endpoints are deprecated?
- As of 30 October 2026, resend.json in resend/resend-openapi marks 4 operations deprecated: DELETE /audiences/{id}, GET /audiences, GET /audiences/{id} and POST /audiences. No compared operation (one the comparison paired with a baseline operation) gained the deprecated flag between 10 April 2026 and 30 October 2026. 4 were already deprecated at the baseline.
- Source: resend/resend-openapi, the two commits compared
- Did any Resend API request fields become required?
- None between 10 April 2026 and 30 October 2026, among the JSON request bodies in resend.json in resend/resend-openapi the comparison could read. A field inside a union (anyOf or oneOf) is not compared, so it is not counted either way.
- Source: resend/resend-openapi, the two commits compared
- Where is the Resend OpenAPI specification?
- In the resend/resend-openapi repository on GitHub. This page reads resend.json at commit 0b2a456 (version 1.5.1), dated 30 October 2026.
- Source: resend/resend-openapi on GitHub
The Action does not check Resend yet
It checks GitHub REST and Stripe. If you want your CI to check the Resend endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.