Delcampe Seller API changelog

All notable changes to the public /v1 Seller API are documented here. The format follows Keep a Changelog; the API is versioned by path (/v1). Subscribe to the Atom feed to be notified of every change.

Breaking changes to a published version are never shipped silently: they are always announced here, and automated contract checks guard every already-released path.

[1.1.0] - 2026-10-06

Added

• GET /v1/sales accepts sort=sold_at_desc to list the newest sales first; sort=sold_at_asc, the default, keeps the oldest-first order. Pass the same sort along with after when paginating.

[1.0.0] - 2026-10-05

First public release of the Delcampe Seller API. It replaces the legacy /rest API for sellers and the tools they use; the reference includes a migration guide with call-by-call mapping tables.

Added

• Authentication with a secret API key in the X-Api-Key header, issued by the API Pass (dk_live_ / dk_test_ prefixes). Several keys can be held at once, so a key rotates without downtime.
• Items: POST /v1/items lists an item for sale (validated synchronously, published asynchronously, outcome on GET /v1/item-submissions/{id}); POST /v1/item-batches lists up to 100 items in one call with partial success; GET /v1/items browses your items with filters and cursor pagination; GET /v1/items/{id}, PATCH /v1/items/{id}, POST /v1/items/{id}/close and POST /v1/items/{id}/restart read and act on one item.
• Sales: GET /v1/sales, your sales with the buyer, the shipping address and the bill reference, filterable by item, bill, date, cancellation and rating status; GET /v1/sales/{id} reads one sale with your rating of its buyer; POST/GET/PATCH /v1/sales/{id}/rating rate the buyer of a sale, read the rating back and revise it.
• Bills: GET /v1/bills (your shipping worklist) and GET /v1/bills/{id}; shipment trackings on GET/POST /v1/bills/{id}/trackings and PATCH/DELETE /v1/bills/{id}/trackings/{tracking_id}, several per bill; POST /v1/bills/{id}/mark-sent declares the shipment.
• Webhooks: POST/GET /v1/webhooks and PATCH/DELETE /v1/webhooks/{id} to manage subscriptions, HMAC-SHA256 signed JSON deliveries for the whole event catalogue (item.*, sale.cancelled, payment.received), and GET /v1/webhook-deliveries to inspect the delivery attempts.
• Account: GET /v1/account and GET /v1/account/limits; every publish response carries X-RateLimit-* / X-StoreLimit-* headers.
• Reference data: GET /v1/categories, GET /v1/shipping-models and GET /v1/delivery-services to resolve the ids an item or a tracking needs.
• Conventions: a JSON envelope (status_code plus data or errors), real HTTP status codes, stable error codes documented in the Errors reference, and an Idempotency-Key header on POST /v1/items and POST /v1/item-batches (honoured for at least 30 days).

Deprecated

• The legacy /rest API. See Deprecations below.

Known issues

Active integration-affecting issues are listed here with their status. None at the moment.

Deprecations

• The legacy /rest API is deprecated as of the /v1 release and will be switched off on 5 October 2027. It stays fully operational until then: migrate call by call with the migration guide in the reference. Every /rest response carries Deprecation and Sunset headers announcing this date, with a Link to the reference.