This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
Add Python POST examples #32
Open
Conversation
This file contains 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
* Add ability to keep campaign ID a secret * Add POST examples for sending test email and sending campaign TODO: * Add ability to replicate campaigns
|
I encourage you to change the title of the PR to make reference to Python. |
|
@deezone Thanks, added Python to PR title. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi MailChimp friends,
Just got done creating some scripts to send daily newsletters and circled back around to make some super simple POST request examples that would have helped me out when I was first getting started with your API. This could also help close out #21 but I'll leave that up to you.
I focused on creating a campaign and sending a test email because those were two basic functions I used a lot during testing and neither can create big problems (like accidentally sending a campaign to a major list).
Also added a requirements.txt, which isn't really needed but could be good for more complex examples in the future.
Thanks for this repo, it's very helpful.
Edit: Please disregard the inordinate amount of commits below. I originally was using this fork for development of new scripts to send daily newsletters but I stripped those out into a new private repo.