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

# Records

Read and manage records in a connected resource. This reference uses reusable project, resource, and model identifiers.

```
https://data.jetadmin.io/projects/{{project_id}}/prod/{{resource_name}}/models/{{model_id}}
```

Use the selected resource's static token in the `Authorization` header. Record fields, required values, filter names, and supported operations depend on your model. Inspect **Data → resource → API** for its exact schema.

### Endpoints

* [List records](/api-reference/records/list-records.md)
* [Create a record](/api-reference/records/create-a-record.md)
* [Retrieve a record](/api-reference/records/retrieve-a-record.md)
* [Update a record](/api-reference/records/update-a-record.md)
* [Delete a record](/api-reference/records/delete-a-record.md)
* [Aggregate records](/api-reference/records/aggregate-records.md)
* [Group records](/api-reference/records/group-records.md)

### Fields and pagination

Records are JSON objects whose keys are model field identifiers. [Record schema](broken://pages/P4mK5h09JpPcytyUzrVM) describes the generic envelopes; sample `id` and `name` fields are illustrative.

Use `page` and `_per_page` for pagination. Lists return `count`, `next`, `previous`, and `results`. Search, sorting, aggregation, and grouping depend on resource support.


---

# 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://docs.jetadmin.io/api-reference/records.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.