---
title: "Delete Renders Route"
method: DELETE
path: "/companies/{company_id}/renders"
tags: ["creatives"]
---

# Delete Renders Route

`DELETE /companies/{company_id}/renders`

## Request

- Base URL: `https://app.zalster.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.zalster.com/companies/{company_id}/renders`
- Auth: none declared

Delete a group of renders — the same filters ``GET …/renders`` takes.

At least one filter is required. A bare ``DELETE …/renders`` would mean
"every creative there is", which is not something anyone should be
able to ask for by forgetting a query string.

Deleting a render is not destroying anything irreplaceable: a render is a
pure function of its template version, the product and its assets, so the
next run — or the next "Render this product" — makes it again. See
``services.creatives.delete_renders`` for why the file goes after the row.

## Path parameters

- `company_id` string, uuid, required: Company id

## Query parameters

- `product_id` string, uuid, nullable
- `template_id` string, uuid, nullable
- `variant` string, nullable

## Response `200`

Successful Response

- RenderDeleteOut: What a delete removed. ``files`` trails ``renders`` when a render never produced one (pending or failed) or its file is shared.
  - `renders` integer, required
  - `files` integer, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zalster/apis/zalster-feed-processor.md) - [All operations](https://skmtc.dev/zalster/apis/zalster-feed-processor/llms.txt) - [OpenAPI document](https://skmtc.dev/zalster/apis/zalster-feed-processor/revisions/d0b9dc66ad36?raw)