OTTO Market

Getting credentials

1. You must already be an OTTO Market partner. In the OTTO Partner Connect portal open the API area and create API credentials for your account.
2. OTTO issues a username and password for the token endpoint rather than a classic client id/secret pair; the token request is a password grant against https://api.otto.market/v1/token.
3. Set OTTO_USERNAME and OTTO_PASSWORD. AnythingMCP exchanges them for an access token and refreshes it automatically.

Every endpoint is versioned separately. OTTO versions per resource, not per API: orders are on /v4/orders, quantities on /v1/quantities, prices on /v3/prices. The tools below carry the version each resource is actually on — do not assume one prefix works everywhere.

Orders page with a cursor. otto_market_list_orders returns nextCursor; pass it back as nextCursor to walk the list. Do not compute an offset; OTTO's order stream is append-only and offsets drift.

fromOrderDate is required and is a hard filter. Asking without it returns the default window, which is much shorter than most people expect. State the date you mean.

Stock and price are eventually consistent. A quantity update is accepted with a 202 and applied asynchronously; reading the value back immediately will often still show the old number. That is OTTO's design, not a failed write.

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.

Writes: otto_market_update_quantity and otto_market_update_price change what shoppers on otto.de see.