Zalando
Zalando is Europe's leading online platform for fashion and lifestyle, connecting customers, brands and partners across more than 20 markets. Its zDirect Platform (formerly the Zalando Partner / Merchant Platform) exposes a suite of REST APIs that let merchants and integration partners manage the full article lifecycle: onboarding and enriching products, submitting attributes, controlling prices and stock, blocking or unblocking offers, managing sales channels and logistic centers, retrieving orders, and operating Zalando Fulfillment Solutions (ZFS) stock movements and cross-border reporting. All APIs are OAuth 2.0 client-credentials protected, follow the widely referenced Zalando RESTful API and Event Guidelines, use JSON (with JSON:API media types on several services), and offer a full sandbox environment. Zalando was surfaced as an HV Capital portfolio company and enriched into the API Evangelist network from its public developer surface.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Zalando the way a machine reads it — 25 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zalando scores 40.5/100 (thin), with a separate agent-readiness read of 72/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Zalando
Each block below is one kind of artifact we hold for Zalando. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Zalando AnnouncedReturns API
The AnnouncedReturns API from Zalando — 1 operation(s) for announcedreturns.
Zalando attribute-types API
The attribute-types API from Zalando — 2 operation(s) for attribute-types.
Zalando attribute-values API
The attribute-values API from Zalando — 2 operation(s) for attribute-values.
Zalando Attributes API
The Attributes API from Zalando — 2 operation(s) for attributes.
Zalando Cross Border Movements API
The Cross Border Movements API from Zalando — 1 operation(s) for cross border movements.
Zalando Discovery API API
The Discovery API API from Zalando — 1 operation(s) for discovery api.
Zalando History of Price Update Attempts API
The History of Price Update Attempts API from Zalando — 1 operation(s) for history of price update attempts.
Zalando Liquidated Items API
The Liquidated Items API from Zalando — 1 operation(s) for liquidated items.
Zalando Logistic Centers API
The Logistic Centers API from Zalando — 2 operation(s) for logistic centers.
Zalando offer-blockers API
The offer-blockers API from Zalando — 2 operation(s) for offer-blockers.
Zalando Orders API
The Orders API from Zalando — 11 operation(s) for orders.
Zalando Outlines API
The Outlines API from Zalando — 2 operation(s) for outlines.
Zalando prices API
The prices API from Zalando — 1 operation(s) for prices.
Zalando Product Association API
The Product Association API from Zalando — 1 operation(s) for product association.
Zalando Reports API
The Reports API from Zalando — 1 operation(s) for reports.
Zalando Returned Items API
The Returned Items API from Zalando — 1 operation(s) for returned items.
Zalando SalesChannels API
The SalesChannels API from Zalando — 1 operation(s) for saleschannels.
Zalando Shipments API
The Shipments API from Zalando — 2 operation(s) for shipments.
Zalando stocks API
The stocks API from Zalando — 1 operation(s) for stocks.
Zalando Types API
The Types API from Zalando — 1 operation(s) for types.
Scroll within the panel for all 20 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
zDirect candidate MCP (derived)
Candidate MCP tool list derived from zDirect OpenAPI operations; no official server published.
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Zalando — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/zalando · machine-readable index on apis.io