# Overview

Records serve as the backbone for storing and managing structured data within the system. They represent various business entities such as customers, transactions, workflows, or any other relevant objects. The system provides a flexible and dynamic structure that allows workflows to interact with records seamlessly.

{% hint style="info" %}
**If you want to use this functionality, our team needs to prepare the appropriate configuration in coordination with you. If needed, please contact us at** [**tech@transactionlink.io**](mailto:tech@transactionlink.io)
{% endhint %}

### Concept of a Record

A record in the API represents a structured data entry stored within the system. Each record possesses a unique `recordId`, which serves as its identifier. Records consist of structured data fields relevant to their type, including but not limited to:

* Customer details
* Order history
* Workflow progress

#### Key Features

* **Unique Identification**: Each record is uniquely identified by a `recordId`.
* **Structured Data Storage**: Records contain fields specific to their type, ensuring data integrity.
* **Workflow Integration**: Workflows can interact with records by reading data, updating fields, or creating new records dynamically during execution.
* **Dynamic Record Creation**: Workflows can start for existing records using a `recordId` or generate new records as part of their execution.
* **Configurable Relationships**: The structure of records and their interconnections are fully configurable, allowing adaptation to diverse business use cases.
* **API Reference**: Due to the configurability of records, the exact API reference is dynamically generated and accessible through the dashboard.

### Flexibility and Configurability

Records are designed to support dynamic structures and relationships tailored to business requirements. The API dynamically generates documentation based on the current system configuration, ensuring up-to-date reference material is always available.

For further details, refer to the API reference documentation accessible within the dashboard.

{% content-ref url="/pages/a89RRSja59QadCvmGf1Q" %}
[Records](/docs/transactionlink-api/api-reference/records.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.transactionlink.io/docs/records/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.