Weave Code
Php Sdk Laravel Package
mailxpert/php-sdk
MailXpert PHP SDK provides a lightweight client for the MailXpert email marketing API, letting PHP and Laravel apps manage contacts, lists, campaigns, and templates. Simple to install via Composer and integrate into existing projects.
mailXpert PHP SDK for API V2.0
Frequently asked questions about Php Sdk
- How do I install the MailXpert PHP SDK with Composer?
- Install it as a Composer dependency using composer require mailxpert/php-sdk. Because the current release is 0.1.0, pin an exact version in composer.json and commit the lockfile so an unattended update cannot move you onto a breaking 0.x release. Before installing, check the package's composer.json constraints against your PHP and Laravel versions.
- Does mailxpert/php-sdk support Laravel package auto-discovery?
- That is unverified from the release artifact, which carries no manifest detail. A conventional Laravel package would declare a service provider for auto-discovery and optionally a facade, but this package may instead be a framework-agnostic PHP SDK that you instantiate manually. Review the source and composer.json before assuming auto-discovery, because manual provider registration is a minor but real integration deviation.
- Which PHP and Laravel versions are compatible with the MailXpert PHP SDK?
- The supported PHP and Laravel versions are not stated in the available release information. Read the composer.json constraint block and run a composer why-not check in a scratch branch against your pinned framework version. Treat integration as feasible but unproven until those constraints are confirmed.
- How do I configure MailXpert API credentials in Laravel?
- The SDK provides a PSR-friendly client setup that takes API credentials, but the exact config keys and environment variable names are not documented in the release detail provided. Review the source or README for constructor and configuration expectations before wiring it into a Laravel service container binding. Keep credentials in environment variables or a secrets manager rather than committing them to config files.
- Can the MailXpert PHP SDK manage contacts, lists, campaigns, and templates?
- Yes, the package is described as an object-oriented wrapper around MailXpert REST endpoints for resources such as contacts, lists, campaigns, and templates. It is intended for automation, synchronization, and custom integrations, so you can call those operations from PHP instead of hand-rolling HTTP requests. Confirm the exact method names and payload shapes against the source before building workflows.
- Is mailxpert/php-sdk safe to use in production at version 0.1.0?
- Treat it as pre-1.0 and unstable: semver allows breaking changes in 0.2.0, so pin an exact version and lock it. The empty 0.1.0 release notes add process risk because there is no documented scope or compatibility floor. A sensible path is a timeboxed spike, then staging behind a feature flag with the package inert by default, and production only after a named owner accepts the upgrade obligation.
- How should I test a Laravel integration with the MailXpert PHP SDK?
- Start with a timeboxed spike in a throwaway branch: install the package, publish or create any required config, and exercise the happy path with non-production credentials. Check whether the SDK ships testing fakes or HTTP mocks; if it does not, isolate calls behind your own adapter so you can mock them in tests. Confirm in staging that the package is inert by default and registers no unexpected middleware, listeners, or scheduled work.
- Does the MailXpert PHP SDK add database tables or require migrations?
- No data model, schema change, or backfill is specified in the release notes, so the package may be stateless config plus runtime hooks. If it is stateless, adoption is additive and reversible; if it introduces tables, review up and down migrations before staging. Establishing this is the first thing to check because it decides whether rollout is a config change or a schema change.
- What are alternatives to the MailXpert PHP SDK?
- The main alternative is calling the MailXpert REST API directly with an HTTP client such as Guzzle, which avoids inheriting a pre-1.0 dependency but means writing and maintaining request handling yourself. You could also evaluate other email marketing SDKs if you are not committed to MailXpert. Compare the SDK's object-oriented convenience against the control and stability of a thin in-house client.
- Who maintains mailxpert/php-sdk and is there a support window?
- The available information does not say whether the maintainer is an individual or a team, and no support window is stated. The empty 0.1.0 release notes are a weak maintenance signal, so weigh changelog discipline and release cadence as process risk independent of code quality. If you adopt it, assign ownership to a named engineer and budget for at least one breaking-change migration before 1.0.
Weaver
How can I help you explore Laravel packages today?