Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Migrating over to the new API will...
API Migration (v2 => v3 endpoint migrations)
Note: Along with the endpoints changing, the data returned from the MailChimp API may differ. This could be either the formatting of the returned data, or the data entirely (new data adding to the api response or data removed from the response that we were using etc.)
API V3 Update
A significant amount of progress was made on the V3 API last week and over the weekend. This message is meant to provide an explanation of the work done so far, as well as the next steps required to complete this task.
A number of new classes have been created. For organization purposes, they have all been added to the
The classes are as follows:
The majority of the old V2 endpoints have been removed from the codebase at this point. There are only a few places where the old V2 endpoints remain:
These locations above should be relatively easy to replace using the existing API methods. Utilizing the existing code as an example should help with converting these endpoints.
There are 2 notable files where there are V2 endpoints remaining. However, these are a special situation, as it appears that there are no endpoints in the V3 API comparable to the endpoints used in the V2 API. Or, there may be a comparable endpoint, but the specific data we're using does not seem to exist in the V3 API.
Evan contacted MailChimp about the missing endpoints and we have an update:
WCUS Meeting Notes
Keep v2 items in that are not being supported in v3 in the API class file.
Affected features not supported by v3: