Skip to main content

Versioning

Early access
Pickware 1.74.0 and later serve the 2026-06-unstable schema, which may still receive breaking changes, each marked in the Pickware changelog.

The Pickware GraphQL API uses date-based schema versions such as 2026-06-unstable. On Shopware 6, the version is not part of the endpoint path: POST /api/graphql always serves the schema that ships with the installed Pickware version. That is the newest stable schema the Pickware version contains, or its newest -unstable schema as long as no stable schema has been released.

Which schema your Pickware version serves​

The installed Pickware version is listed in the Shopware administration under Extensions → My extensions. Each schema has its own generated reference.

Pickware versionSchema served at /api/graphql
Pickware 1.74.0 – current2026-06-unstable

Updating Pickware​

The schema an integration talks to only changes when Pickware is updated. A Pickware release that moves the endpoint to a newer schema is marked as a breaking change in the Pickware changelog, and so is every breaking change within an -unstable schema. After such an update, the administration shows a notification if a token was used in the last 30 days.

Before updating, compare the reference of the new schema with the fields, inputs, and mutations your integration uses, and update the integration together with Pickware.

Compatibility expectations​

Schemas with the -unstable suffix are early-access previews and may change in incompatible ways between releases: fields can be renamed or removed, input shapes can change, and mutations may be redesigned.

Once a schema is published without the -unstable suffix, integrations can rely on documented fields, inputs, and mutations within that version. Additive changes such as new fields or enum values may still appear in stable versions, so design clients to tolerate them: ignore unknown fields and handle unrecognized enum values gracefully rather than treating them as errors.