This is a PHP library for version 3.0 of MailChimp's API
This library assumes a basic understanding of the MailChimp application and its associated functions.
There are two ways you can include this library in your project. One is through Composer and the other is by cloning this repository and manually including src/mailchimpRoot.php
.
For Composer run:
composer require jhut89/mailchimp3php
Then run composer update
and add composer autoloader to your project with:
require "vendor/autoload.php";
To manually include this library you can clone https://github.com/Jhut89/Mailchimp-API-3.0-PHP.git
and use it with:
require '/path/to/mailchimpRoot.php';
The only file that you need to require is mailchimpRoot.php. The file structure for this library should not be altered as its usage depends upon it.
$mailchimp = new Mailchimp('123abc123abc123abc123abc-us0');
To instantiate you will need a new instance of the Mailchimp
class with your MailChimp account's API key as its only argument.
If you are using Oauth to obtain an access token, this library can handle the "handshake" for you.
You must first send the user to the authorize_uri
. You can get this url like this:
$client_id = '12345676543';
$redirect_url = 'https://www.some-domain.com/callback_file.php';
Mailchimp::getAuthUrl($client_id, $redirect_url);
Then the user will input their username and password to approve your application and will be redirected to the redirect_uri
you set along with a code
.
Since you do not yet have an API key you will need to call the oauthExchange()
method statically like this:
$code = 'abc123abc123abc123abc123';
$client_id = '12345676543';
$client_secret = '789xyz789xyz789xyz789xyz';
$redirect_url = 'https://www.some-domain.com/callback_file.php';
Mailchimp::oauthExchange($code, $client_id, $client_secret, $redirect_url);
If the handshake is successful, then this method will return a string containing your API key like this: 123abc123abc123abc123abc123abc-us0
. This API key can now be used to instantiate your Mailchimp
class as we have above.
Once you have instantiated the Mailchimp
class you can start constructing requests. Constructing requests is done by 'chaining' methods to the $mailchimp
instance. In most cases this 'chain' will end with the HTTP verb for your request. So an example of retrieving a lists collection would look like this:
$mailchimp->lists()->GET();
Retrieving an instance can be accomplished by giving a unique identifier for the instance you want as an argument to the appropriate method. For example if I wanted to retrieve a list instance from the above example I would simply pass a list_id
, as the only argument for the lists()
method. Like this:
$mailchimp->lists('1a2b3c4d')->GET();
Methods available for each position in the chain depend on what the prior method returns. For example if I wanted to retrieve subscribers from a list in my account I would:
$mailchimp->lists('1a2b3c4d')->members()->GET();
Notice that I provided a list_id
to the lists()
method, as there would be no way to retrieve a list of subscribers from a lists collection. The above request however will only return 10 subscriber instances from the members collection. This is because MailChimp's API uses pagination (documented HERE) that defaults to count=10
and offset=0
. This library allows you to alter query string parameters by by passing them as an argument to the GET()
method. We do this by providing an array of key-value pairs where the keys are the query parameter you wish to provide/alter and its value is the parameter's value. As an example if I wanted to retrieve the second 100 subscribers from my list I could:
$mailchimp->lists('1a2b3c4d')->members()->GET([ "count" => "100", "offset" => "100"]);
This would be equivalent to making a get request against:
Https://us0.api.mailchimp.com/3.0/lists/1a2b3c4d/members?count=100&offset=100
Going a little further we can retrieve a single list member by giving the members_hash
(md5 hash of lower-case address) to the members()
method. Like this:
$mailchimp->lists('1a2b3c4d')->members('8bdbf060209f35b52087992a3cbdf4d7')->GET();
While being able to retrieve data from your account is great we also need to be able to post new data. This can be done by calling the POST()
method at the end of a chain. As an example subscribing an address to a list would look like this:
$post_params = ['email_address'=>'example@domain.com', 'status'=>'subscribed'];
$mailchimp->lists('1a2b3c4d')->members()->POST($post_params);
In this case I would not provide members()
with an identifier as I want to post to its collection. Also notice that the post data is an array of key-value pairs representing what parameters I want to pass to the MailChimp API. Be sure that you provide all required fields for the endpoint you are posting to. Check MailChimp's documentation for what parameters are required. Non-required parameters can just be added to the post data, and MailChimp will ignore any that are unusable. To illustrate here is an example of adding a subscriber to a list with some non-required parameters:
$merge_values = array( "FNAME" => "John", "LNAME" => "Doe" );
$post_params = array("email_address" => "example@domain.com", "status" => "subscribed", "email_type" => "html", "merge_fields" => $merge_values )
$mailchimp->lists('1a2b3c4d')->members()->POST($post_params);
This library handles PUT and PATCH request similar to that of POST requests. Meaning that PUT()
& PATCH()
both accept an array of key-value pairs that represent the data you wish altered/provided to MailChimp. As an example if I was patching the subscriber that we subscribed above, to have a new first name, that would look like this.
$mailchimp->lists('1a2b3c4d')->members('a1167f5be2df7113beb69c95ebcdb2fd')->PATCH( [ "merge_fields" => ["FNAME" => "Jane"] ] );
Deleting a record from MailChimp is performed with the DELETE()
method and is constructed similar to GET requests. If I wanted to delete the above subscriber I would:
$mailchimp->lists('1a2b3c4d')->members('a1167f5be2df7113beb69c95ebcdb2fd')->DELETE();
mailchimp()
|
|----account()
|
|----apps()
|
|----automations()
| |
| |----removedSubscribers()
| |----emails()
| |
| |---queue()
| |---PAUSE_ALL()
| |---START_ALL()
|
|----batches()
|
|----batchWebhooks()
|
|----campaignFolders()
|
|----campaigns()
| |
| |----CANCEL()
| |----PAUSE()
| |----REPLICATE()
| |----RESUME()
| |----SCHEDULE()
| |----SEND()
| |----TEST()
| |----UNSCHEDULE()
| |----checklist()
| |----feedback()
| |----content()
|
|----conversations()
| |
| |----messages()
|
|----ecommStores()
| |
| |----customers()
| |----products()
| | |
| | |----variants()
| | |----images()
| |
| |----orders()
| | |
| | |----lines()
| |
| |----carts()
| |
| |----lines()
|
|----fileManagerFiles()
|
|----fileManagerFolders()
|
|----lists()
| |
| |----BATCH_SUB()
| |----webhooks()
| |----signupForms()
| |----mergeFields()
| |----growthHistory()
| |----clients()
| |----activity()
| |----abuseReports()
| |----segments()
| | |
| | |----BATCH()
| | |----members()
| |
| |----members()
| | |
| | |---notes()
| | |---goals()
| | |---activity()
| |
| |----interestCategories()
| |
| |----interests()
|
|----reports()
| |
| |----unsubscribes()
| |----subReports()
| |----sentTo()
| |----locations()
| |----emailActivity()
| |----eepurl()
| |----domainPerformance()
| |----advice()
| |----abuse()
| |----clickReports()
| |
| |----members()
|
|----searchCampaigns()
|
|----searchMembers()
|
|----templateFolders()
|
|----templates()
|
|----defaultContent()
*Please see MailChimp's API Documentation for what verbs are appropriate where.
This library offers several setting that can be altered by changing the value of the class constants at the begining of the Mailchimp
class in the mailchimpRoot.php
file. Be sure to check them out to see if they can be altered to fit your project a little better.
This library has a very small debug function that will allow you to output some request information and what was returned. This can be turned on by setting:
const DEBUGGER = true;
The debugger can also log to a file if you provide a file for it to write to using const DEBUGGER_LOG_FILE
like this:
const DEBUGGER_LOG_FILE = 'path/to/some/file.php';
By default this option is set to false
.
CURLOPT_SSL_VERIFYPEER
can be disabled by setting:
const VERIFY_SSL = false;
By default this option is set to true
.
To include the returned headers in the output from this library set:
const HEADERS = true;
By default this option is set to false
.
**Please watch for updates, and feel free to Fork or Pull Request. Check out the Wiki for a little more info on contributing.