docs: add received_for to inbound email responses#69
Open
platoresend wants to merge 2 commits into
Open
Conversation
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
1 participant
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.
Context
Slack thread
Opened on behalf of: @lucasfcosta
What
Documents the new
received_forfield (merged in resend-monorepo #4637) in the OpenAPI spec.GetReceivedEmailResponse— addsreceived_for(array of strings) to the retrieve-received-email response.EmailReceivedEventData— addsreceived_forto theemail.receivedwebhook payload.Why
The field is already returned by the GET
/emails/receiving/:idroute and theemail.receivedwebhook, but wasn't described in the spec.How
Edited
resend.yamlonly (resend.jsonis auto-generated on push to main).