> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/api/deleting-resources.md).

# Deleting resources

Deletes are permanent unless an endpoint says otherwise; 3D scenes and 3D templates move to the trash. Where a resource has a `:delete` scope (for example `contacts:delete`), deleting needs that scope — write access alone does not delete. Cancelling a pending customer invitation and deleting custom-field definitions use their write scopes.

Deleting a resource by id answers 404 when it does not exist. Removing state from a resource — cancelling an invitation, deleting a custom-field definition, revoking a contact's portal access — succeeds when there is nothing left to remove, so a retried call stays a success.

Removing a member from a collection, category, gallery or product group changes that relationship; it does not delete the referenced resource. An empty replacement list can remove all members, so read each operation's replacement rules before writing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.mimeeq.com/api/deleting-resources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
