Weave Code
Mailchimp Lib Laravel Package
ebizmarts/mailchimp-lib
ebizmarts/mailchimp-lib is a PHP library for integrating applications with the MailChimp API. It provides wrappers for managing lists, subscribers, campaigns, and e-commerce data, simplifying MailChimp synchronization in PHP projects.
API client library for the MailChimp
Frequently asked questions about Mailchimp Lib
- How do I install ebizmarts/mailchimp-lib in a Laravel application?
- Install it with Composer by running composer require ebizmarts/mailchimp-lib from your Laravel project root. The package is a plain PHP library, so there is no Laravel auto-discovery step or published config file. After installation you can instantiate its classes directly in controllers, jobs, or a small service class of your own. Commit the updated composer.json and composer.lock so other environments get the same version.
- Does ebizmarts/mailchimp-lib work with Laravel 10 and 11?
- It is framework-agnostic PHP rather than a Laravel package, so compatibility depends mainly on the PHP version your application runs and the library's own PHP constraint. Check the package's composer.json on Packagist for that requirement before upgrading Laravel. In practice most current Laravel releases can use it as long as the PHP constraint is satisfied.
- Is there a service provider or facade for MailChimp in this package?
- No, ebizmarts/mailchimp-lib does not ship a Laravel service provider or facade. You register it yourself, for example by binding a configured client instance in a custom service provider or resolving it through a dedicated wrapper class. That extra step is small but gives you cleaner dependency injection and easier testing.
- How do I store the MailChimp API key in a Laravel app using this library?
- Keep the API key out of source control by placing it in your .env file and reading it with env() only inside config files such as config/services.php. The library expects credentials when you construct its client, so pass the config value in at that point. Run php artisan config:cache in production and never log the key.
- Can I manage MailChimp lists and subscribers with this library?
- Yes, the package provides wrappers for MailChimp list and subscriber operations, which is a core part of its stated purpose. You can use those wrappers for tasks like syncing new signups, updating merge fields, or handling unsubscribe flows. Because the library maps closely to MailChimp's API, still review MailChimp's endpoint documentation for required fields and limits.
- Does ebizmarts/mailchimp-lib support MailChimp e-commerce endpoints?
- The package description states it includes wrappers for e-commerce data alongside lists, subscribers, and campaigns. That makes it usable for syncing customers, orders, and products with a connected MailChimp store. Verify the specific e-commerce calls you need against your current MailChimp API version before building on them.
- How can I test MailChimp integration without calling the live API?
- Wrap the library calls in your own service class and mock that class in your Laravel tests so no real HTTP requests are made. For integration tests, use a dedicated MailChimp test audience or account rather than a production list. Keep API-key-dependent tests out of CI or gate them behind environment variables.
- What are the alternatives to ebizmarts/mailchimp-lib for Laravel?
- You can use the official MailChimp Marketing PHP SDK, or a Laravel-specific wrapper package that adds a facade and publishable config. Some teams call the MailChimp REST API directly with Laravel's HTTP client to avoid an extra dependency. Compare maintenance activity and API version support before choosing.
- Is ebizmarts/mailchimp-lib still maintained?
- Maintenance can vary, so check the latest release date and commit history on the package's Packagist and repository pages before adopting it. If the project has gone quiet, confirm it still targets the MailChimp API version you use. For long-lived applications, pin a version and be prepared to fork or migrate.
- How should I handle MailChimp API errors and rate limits in production?
- Expect failures such as invalid subscribers, authentication errors, and MailChimp rate limiting, and catch exceptions around every library call. Queue non-urgent syncs as Laravel jobs with retries and backoff instead of calling the API during web requests. Log enough context to debug, but never log API keys or full subscriber payloads.
Weaver
How can I help you explore Laravel packages today?