Delete a product
DELETE /api/v0/products/{id} removes one stored product, with all its variants, from Releva’s catalog.
When to use it
Section titled “When to use it”Call it when a product is permanently removed from your catalog. It is permanent: there is no undelete, and the only way to bring a product back is to send it again. A product that is only out of stock or hidden for a while should stay: send it with available: false through Create or update products or Update product availability. It keeps its history, and it fires a back-in-stock catalog event when it returns. A deleted product cannot trigger anything.
If Releva also pulls your catalog, a product your endpoint stops returning is deleted after the next complete sync anyway. See Let Releva pull your catalog.
Authentication
Section titled “Authentication”Send your shop’s Secret Key as a bearer token: authorization: Bearer $RELEVA_SECRET_KEY. Find it under Settings › Shop & Integration (Find your Access Token and Secret Key). The error messages are in Catalog API: Authentication.
Request
Section titled “Request”DELETE https://releva.ai/api/v0/products/{id}. There is no body.
{id} is the stored product id, exactly as you sent it to POST /products, character for character, including any language or market suffix. Nothing else matches: not your internal SKU, not a product id derived from it, not a custom field. Percent-encode reserved characters. Each language or market version is its own product: delete each id, for example DEMO-1001_en and DEMO-1001_de.
There is no call that deletes one variant. To stop selling a single variant, send the product to Create or update products with that entry removed from variants, or with its available set to false. If you send each variant as its own product (the older style described in Create or update products), delete them one at a time by their own ids.
curl -X DELETE 'https://releva.ai/api/v0/products/DEMO-1001' \ -H "authorization: Bearer $RELEVA_SECRET_KEY" \ -H 'content-type: application/json'Response
Section titled “Response”202 Accepted with the body {}. The delete is queued and runs a few seconds later. An id that is not in the catalog also answers 202 and changes nothing, so the call is safe to repeat.
Errors
Section titled “Errors”Only authentication errors apply, plus:
| Status | When | Message |
|---|---|---|
400 |
Authentication failed | See Catalog API: Authentication |
402 |
Your shop is disabled | Domain is disabled. Please reach out to support@releva.ai to enable it. |
500 |
Unexpected error; retry later | An internal error occurred. |
Limits
Section titled “Limits”- One product per request.
- Rate limits: none.