Withdraw a published DPP (Approved -> Withdrawn -> public 410)
POST/api/v1/products/:id/withdraw
Required scope: dpp:withdraw (distinct least-privilege scope — it pulls
already-published content offline). A WRITE (HMAC + Idempotency-Key).
The public DPP flips to HTTP 410 Gone within the cache tick. Per
EU Battery Reg Art. 76(2) / GPSR Art. 19: a successorProductId is
REQUIRED for reasons EndOfLife / MarketWithdrawal / Supersession, and
Recall / Counterfeit carry the 24h regulator-notify metadata
(regulatorNotifiedAuthority). The successor must be your own product or
a publicly Approved DPP.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 503
Withdrawn
400 — INVALID_JSON, VALIDATION_ERROR, or IDEMPOTENCY_KEY_REQUIRED.
401 — INVALID_SIGNATURE or SIGNING_NOT_CONFIGURED (or bearer auth failure).
403 — missing scope (FORBIDDEN_SCOPE) or module (FORBIDDEN_MODULE).
404 — not found OR owned by another tenant (NOT_FOUND; IDOR-safe).
Product is not in a withdrawable state (INVALID_STATE).
Successor invalid (SUCCESSOR_INVALID) or demo product (DEMO_PRODUCT).
429 — RATE_LIMITED (per-key limit, reads and writes alike; fails closed,
so a limiter outage also returns 429). A limiter-down 429 is deliberately
indistinguishable from a quota 429. Carries Retry-After (seconds).
Response Headers
Seconds to wait before retrying (429 only).
Per-minute request ceiling for this key's tier.
Requests left in the current window (floored at 0).
Seconds until the window resets.
503 — the API is not enabled on this environment (FEATURE_DISABLED).