Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I noticed the documentation said a recipients array will replace the … #185

Merged
merged 2 commits into from
May 29, 2019

Conversation

possnfiffer
Copy link
Contributor

@possnfiffer possnfiffer commented Nov 18, 2018

…current recipients so I wrote this functionality to overcome that as being able to add a single recipient is useful.

This is the line in the documentation I'm talking about

If a recipients array is provided in the update request, it will replace the current recipients. This means that if you're adding, updating, or removing a single recipient, the recipients array must contain all current recipients, regardless they are being changed or not.

It comes from this URL [Recipient Lists - Documentation](https://developers.sparkpost.com/api/recipient-lists/#recipient-lists-put-update-a-recipient-list]

possnfiffer added 2 commits November 18, 2018 06:10
…current recipients so I wrote this functionality to overcome that as being able to add a single recipient is useful.
…cipients.py

oops, forgot to include the print(response) like the other examples do
Copy link
Contributor

@jgzamora jgzamora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@jgzamora jgzamora merged commit 686873b into SparkPost:master May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants