Weave Code
Shopware Sdk Laravel Package
it-bens/shopware-sdk
A PHP SDK for the Shopware 6 Admin and Store APIs, providing typed request builders, response hydration, and PSR-18 client integration so you can query products, orders, and customers without hand-writing endpoints.
it-bens/shopware-sdk is a PHP client library for the Shopware 6 Admin and Store APIs, generated from the official OpenAPI specifications. It provides strongly typed request and response objects instead of raw arrays, so IDE autocompletion and static analysis catch mistakes before runtime. The SDK is framework-agnostic and built around PSR-18 HTTP clients and PSR-17 factories, letting it slot into Laravel, Symfony, or any other PSR-compatible stack without extra adapters.
- Type-safe DTOs for Shopware endpoints, generated from upstream schemas
- PSR-18/PSR-17 compatible — bring your own HTTP client
- Framework-agnostic, with no Laravel or Symfony lock-in
- Serializer integration for JSON payload (de)serialization
- Broad API coverage across Admin and Store endpoints in one package
Frequently asked questions about Shopware Sdk
- Is it-bens/shopware-sdk a Laravel package or a standalone PHP SDK?
- It is a thin, object-oriented PHP client for the Shopware 6 Admin API and Store API, not a Laravel package. Metadata shows no service provider, facade, or publishable config, so Laravel support comes from wiring it in yourself. In a Laravel app you would typically bind it as a singleton in a service provider and inject it into sync, import, or export services.
- How do I install it-bens/shopware-sdk with Composer?
- Install it with composer require it-bens/shopware-sdk. Before committing, read the package composer.json to confirm its PHP and dependency constraints against your runtime. It is MIT licensed and registers nothing automatically in Laravel, so installation is just the dependency plus your own wiring.
- How do I configure the Shopware 6 Admin API client in Laravel?
- There is no config file to publish, so create your own config/shopware.php or environment variables for the shop URL, client ID, and client secret. Register the client as a singleton in a service provider so connections and auth tokens are reused across requests and queued jobs. Then inject it into the classes that talk to Shopware.
- Does this SDK handle Shopware 6 OAuth2 authentication and token refresh?
- The Shopware 6 Admin API uses an OAuth2 client-credentials flow, and token lifecycle is the most common failure point in Shopware integrations. Check the source to confirm whether the SDK performs the token request and refresh for you or expects a token to be passed in. If it does not, wrap the client with your own token cache and refresh logic so queued workers do not re-authenticate on every job.
- Which PHP and Shopware 6 versions does it-bens/shopware-sdk support?
- Version support is defined by the package composer.json, and because this is a fork of older upstream code the constraints may lag behind PHP 8.3 and 8.4. Read that file rather than assuming compatibility with your Laravel runtime. Also check whether the maintainer states a tested Shopware 6 minor range, since the Admin API evolves across minor releases.
- Does it-bens/shopware-sdk use Guzzle or Laravel's HTTP client?
- Check the composer.json to see whether it depends on Guzzle, Symfony HttpClient, or a PSR-18 implementation. If it bundles its own HTTP client, you get a parallel stack that sidesteps Laravel's retries, proxy settings, and HTTP event hooks. That matters for logs, metrics, and rate limiting around Shopware calls.
- What Shopware endpoints does this SDK cover?
- Forked SDKs usually cover the endpoints the original author needed, so coverage may be partial. Enumerate your required operations, such as products, variants, media, categories, orders, customers, and price rules, against the SDK's endpoint classes before approval. If you only need one or two calls, Laravel's HTTP client is lighter and avoids the abstraction cost.
- Is it-bens/shopware-sdk maintained, and how does it differ from vin-sw/shopware-sdk?
- It is a fork of vin-sw/shopware-sdk with a release around January 2025 and very low adoption, so there is little ecosystem validation. Compare its commit history and changelog against upstream to see how far it diverged and whether upstream fixes are being carried forward. Treat fork liability as the main risk: if upstream is abandoned, this fork becomes the only lifeline.
- Should I use this SDK or call the Shopware Admin API directly from Laravel?
- For an integration with more than roughly ten distinct Shopware operations, the typed request and response objects pay off by centralizing serialization, associations, and search criteria building. For a narrow integration of one or two endpoints, Laravel's native HTTP client is lighter and carries no fork risk. Either way, wrap the SDK behind your own interface so it can be swapped out later.
- How should I test and run a Shopware integration built on this SDK in production?
- No test suite or CI is visible from the metadata, so build contract tests against a staging Shopware instance or a mocked HTTP layer. In production, cache OAuth tokens, add retries and timeouts around the SDK, and log failed Admin API responses. Track Shopware minor releases closely, because an SDK without active compatibility testing will drift silently.
Weaver
How can I help you explore Laravel packages today?