kaufland.com valid

Kaufland Marketplace Seller API

HTTP interface to the Kaufland Global Marketplace for sellers and technology partners. It covers

For agents: REST Seller API for the Kaufland Global Marketplace: auth, pagination, storefronts, full OpenAPI reference; endpoints hit live production data.

marketplace seller apikauflandrest apiopenapiseller integration

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T13:35:18.854Z. Cached copy · Source on kaufland.com

# Kaufland Marketplace Seller API

> HTTP interface to the Kaufland Global Marketplace for sellers and technology partners. It covers
> product data, inventory, orders, invoices, returns, tickets, reports and vouchers, through either
> a REST API (version 2) or a bulk file interface (CSV and XML).

Production REST endpoints live under `https://sellerapi.kaufland.com/v2/` and require HTTPS; the
Playground is a separate host, described further down. There is no anonymous access: every request
is authenticated with a `Client Key` (32 hexadecimal characters) and signed with a `Secret Key` (64
characters), both issued per seller account. Lost keys cannot be recovered and must be regenerated.

Every request must send five headers: `Accept: application/json`, `Shop-Client-Key`,
`Shop-Timestamp` (current Unix time in seconds), `Shop-Signature`, and a `User-Agent`, which must be
the name of the software solution for technology partners or the literal string
`Inhouse_development` for a seller's own custom integration. `POST` and `PATCH` additionally require
`Content-Type: application/json`. The timestamp must be within 5 minutes of server time in either
direction or the request is rejected.

The signature is an SHA-256 HMAC keyed with the Secret Key over four values joined by newlines:

```
METHOD\nFULL_URI\nBODY\nTIMESTAMP
```

The digest is transmitted as lowercase hexadecimal, 64 characters. `FULL_URI` is the absolute URI
including scheme, host and query string, exactly as sent, not just the path. Omitting the query
string is the most common cause of a rejected signature. `BODY` is the empty string when there is
none.

Technology partners, meaning software providers integrating on behalf of multiple sellers,
authenticate with two credential pairs at once rather than one. The seller's keys still populate
`Shop-Client-Key` and `Shop-Signature`, identifying which seller the call acts for. The partner's
own keys populate two additional required headers, `Shop-Partner-Client-Key` and
`Shop-Partner-Signature`. Both signatures cover the identical canonical string; only the key
differs, so a partner integration computes the same HMAC twice, once with the seller Secret Key and
once with the partner Secret Key. Partner credentials are issued after registering a technology
partner account, separately from the seller account credentials, and both are needed before any
partner call will succeed.

Successful responses are JSON wrapped in a `data` envelope, either a single object or an array. Only
`GET` returns a body. Collections are paged with the `limit` and `offset` query parameters and carry
a `pagination` object with `offset`, `limit` and `total`; defaults and maximums for `limit` are per
endpoint. Some endpoints accept an `embedded` parameter taking a comma-separated list of related
resources to inline.

Country-specific endpoints take a `storefront` parameter, matched case-insensitively, and
language-specific ones take a `locale` parameter such as `de-DE`. All
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=kaufland.com · GET /v1/domain/kaufland.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for kaufland.com:
1. POST https://agentwebmap.com/v1/sites/kaufland.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kaufland.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/kaufland.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kaufland.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.