Zalando Partner (ZDS)

Partner onboarding required. Zalando's merchant APIs are not open: you need an active Zalando Partner Programme contract and credentials issued through Zalando zDirect. There is no self-service signup and no public sandbox, so this adapter ships unverified by design.

Setup

1. In zDirect open the API section and create an OAuth 2.0 client for your merchant account. You receive a client id and client secret.
2. Note your merchant id — a UUID that scopes every path. Zalando merchants often have several (one per sales channel or country), and the wrong one returns an empty, entirely convincing result.
3. Set ZALANDO_CLIENT_ID, ZALANDO_CLIENT_SECRET and ZALANDO_MERCHANT_ID.

Client credentials, scoped per API. The token endpoint is https://api.zalando.com/oauth2/token and the scopes you were granted determine which of the paths below actually answer. A 403 here usually means a missing scope rather than a bad secret.

ZDS vs Partner Fulfilment. These tools target Zalando Direct Ship, where the merchant ships to the customer. Merchants on Zalando Fulfilment Solutions (ZFS) use a different set of endpoints for stock and shipping, because Zalando holds the inventory.

Dates are ISO 8601 with a zone. Order lists are cursor-paged: pass back the next token from the response rather than computing an offset.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.