feat: add broadcasts/{id}/recipients endpoint - #97
Merged
Conversation
dielduarte
marked this pull request as ready for review
August 21, 2026 19:59
gabrielmfern
approved these changes
Aug 21, 2026
| object: | ||
| type: string | ||
| description: Type of the response object. | ||
| example: list |
Member
There was a problem hiding this comment.
I wonder if we should be more explicit here when the value is a constant. Here it's always "list", right?
Contributor
Author
There was a problem hiding this comment.
yeah by convention its always list, but something we can improve for sure. would help with code gen/docs later
This was referenced Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GET /broadcasts/{id}/recipients, matching the current public-api handler (apps/public-api/src/routes/broadcasts/recipients.ts)type(required, event-type enum),email,bounce_type(valid only withtype=bounced), plus standard cursor paginationid(opaque pagination cursor),contact_id(nullable),email,count(opened/clicked only),bounce_type(bounced only),clicked_links(clicked only)Tracked by DEV-1869.
Note: the endpoint is currently gated behind the
headless-dashboardfeature flag in public-api — worth confirming that gate is lifted before/alongside this going live in docs.Test plan
yq -o=json resend.yamlparses cleanlyredocly lint— 0 new errors (10 pre-existing, unrelated to this change); 1 warning (missing 4XX response), consistent with every other endpoint in this spec