Zalando Partner (ZDS)
Zalando's partner APIs for Zalando Direct Ship merchants: orders, order items, shipments, returns, stock and price feeds. OAuth 2.0 client credentials. Partner onboarding required.
7 天免费 · 无需信用卡 · EU 托管
问 Zalando 任何事
通过 AnythingMCP 对 Zalando Partner (ZDS) 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 ZalandoClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Zalando Partner (ZDS)。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
配置 Zalando Partner (ZDS)
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
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
- 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.
- 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.
- Set
ZALANDO_CLIENT_ID,ZALANDO_CLIENT_SECRETandZALANDO_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.