Restore a soft-deleted listing
Undoes DELETE /api/items/{id} inside the 7-day window. The item returns to the status it held before the delete, except that a previously reserved item comes back available (the reservation that justified it is long gone) and an item that no longer fits the seller's active-item limit comes back inactive rather than being refused. Pass an Idempotency-Key: this operation is NOT self-idempotent, and a retry without one reports 409 "This item is not deleted" for a restore that in fact succeeded.
Request
- Base URL: https://clearlist.me
- URL: https://clearlist.me/api/items/{id}/restore
- Auth: one of:
- API key in header X-ClearList-API-Key
- OAuth 2 (authorization code, authorization URL https://clearlist.me/oauth/authorize, token URL https://clearlist.me/api/oauth/token, scopes: write)
Headers
Unique client-generated key (1-255 chars from A-Za-z0-9_-:.; a UUID works well), scoped to the seller and the operation. The first successful (2xx) response is stored for 24h; retrying the identical request with the same key replays it instead of re-executing, so network-failure retries never create duplicates. A duplicate that arrives while the first is still running gets 409 idempotency_conflict. The same key with a different body (byte for byte) or a different kind of credential gets 422 idempotency_key_reuse and leaves the original record in place: send a new key. An error the operation itself returns is never stored and releases the key.
Response
Restored.
Changes
No recorded changes to this operation across all 1 revision of this API.