> For the complete documentation index, see [llms.txt](https://taas-docs.stokr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taas-docs.stokr.io/api-overview/common-data-concepts.md).

# Standard operations

While each resource serves different business purposes, they all share common fields and actions that work consistently across the platform.

## Deactivation (soft delete)

Instead of permanently deleting resources, we use deactivation to preserve data for audit and compliance purposes while preventing further use.

Each resource has deactivation and reactivation endpoints accessed via `PATCH .../resource/:id/deactivate` and `PATCH .../resource/:id/reactivate` .

Deactivation affects the following parameters:

* `active` parameter switches to `false`
* `deactivated_at` parameter records the timestamp of deactivation
* `deactivation_reason` parameter carries a free-text explanation (optional field for your audit records in the request body of deactivation request)

When a resource is deactivated:

* You can still retrieve it via `GET` endpoints (both individual and list views), and it is still shown in lists by default
* Most API actions will verify that resources are active before allowing operations

Reactivation is available if you accidentally deactivate a resource. Depending on the resource type, additional checks may apply before allowing deactivation or reactivation.

## External reference

Most resources support an `external_reference` string parameter to help you maintain connections between our platform and your internal systems. Use this field to store your own system's ID for the resource, making data synchronization easier.

## Audit trails access

Since our platform tracks all changes for compliance and regulatory reasons, each resource provides a dedicated `GET .../resource/:id/events` endpoint to view its complete change history.

Each event record includes:

* Type of event that occurred
* Precise timestamp of the event
* Content of the change driven by this event
* User who performed the action, triggering the event

{% hint style="info" %}
Remember that audit trail accuracy depends on how you manage user accounts. If multiple employees share the same API credentials, our audit trails can't distinguish which specific person made each change.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://taas-docs.stokr.io/api-overview/common-data-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.