- How do I install nztim/mailchimp in a Laravel application?
- Install it with Composer using composer require nztim/mailchimp, then publish the package configuration if you want to customise defaults. The package registers a service provider and exposes a Mailchimp facade, so no manual bootstrapping is required on supported Laravel versions. Before installing, confirm the package's declared Laravel and PHP constraints against your project, since older community wrappers often lag the newest framework releases.
- Which PHP and Laravel versions does nztim/mailchimp support?
- Support depends on the constraints declared in the package's composer.json, so check Packagist and the repository rather than assuming. The package is a maintained fork lineage of drewm/mailchimp-api, so its Laravel and PHP ranges may trail the current framework versions. If your application runs Laravel 11 or newer and the package has not been updated, you may need a fork or a version constraint adjustment.
- How do I configure the Mailchimp API key and server prefix?
- After publishing the config file you set MAILCHIMP_APIKEY and MAILCHIMP_SERVER in your .env file, and the service provider builds the singleton client from those values. Authentication is Mailchimp basic auth over HTTPS using the key, so there is no OAuth flow to implement. Keep the key out of version control and use separate keys per environment to avoid cross-contaminating audiences.
- Can I use nztim/mailchimp outside of Laravel, in plain PHP?
- The underlying client is a standard PHP Mailchimp Marketing API v3 wrapper, so it can be used standalone by instantiating it with your API key and server prefix. The Laravel service provider and facade are conveniences layered on top, not requirements. In a non-Laravel codebase you lose only the config and container integration, while the raw get, post, patch, and delete methods remain available.
- How do I subscribe a user to a Mailchimp audience with this package?
- Use the convenience methods for list and member operations, or call the raw post method against the lists and members endpoints with your own payload. For simple audience syncs, subscribes, tag updates, and merge field changes, the wrapper's abstraction level is appropriate. For anything deeper such as customer journeys or e-commerce data, expect to hand-write payloads against Mailchimp's documentation.
- Should I use nztim/mailchimp or the official Mailchimp Marketing PHP SDK?
- The official mailchimp/marketing SDK is maintained by Mailchimp and is the safer default if coverage and long-term support matter most. This package wins on Laravel ergonomics, with a facade, config publishing, and a familiar method surface, but it adds an extra dependency hop. If your organisation already uses the official SDK elsewhere, standardise on one client rather than running both.
- Is nztim/mailchimp actively maintained and safe for production?
- It is a thin wrapper with a small star count and a single-maintainer profile, so it is not on a strong release cadence. Before adopting it, confirm the last commit and tagged release, whether the maintainer has responded to issues in the last six to twelve months, and whether the upstream project it forks is still patched. Budget a small contingency for forking or patching if upstream goes dormant mid-project.
- How do I handle Mailchimp API errors and rate limits with this wrapper?
- The wrapper exposes raw get, post, patch, and delete calls, so HTTP error handling, retry logic, and rate-limit backoff remain your responsibility. Wrap Mailchimp calls in your own service layer that translates exceptions into domain-level errors and applies exponential backoff on 429 responses. This also protects you from schema drift in the Mailchimp API, which the wrapper does not abstract away.
- Can I manage campaigns and pull reports with nztim/mailchimp?
- Yes in the sense that the raw request methods let you hit the campaigns and reports endpoints of the Mailchimp Marketing API v3. The package provides convenience helpers for common list and subscriber operations, but campaign and report payloads are largely up to you. For heavy reporting needs, check whether the official SDK or a dedicated reporting tool better fits your footprint.
- How do I test a Laravel Mailchimp integration without hitting the live API?
- The package does not ship a built-in fake, so bind a mock of the client in the Laravel container or swap the facade for a test double in your test suite. Because the client uses Guzzle under the hood, faking HTTP responses is another practical option for integration tests. Whichever approach you take, wrap facade calls in your own MailchimpService so your tests target a stable internal interface rather than the vendor package directly.