> For the complete documentation index, see [llms.txt](https://docs.myjson.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myjson.online/terminology/record.md). # Record A **record** is a self-contained unit of data that contains data in JSON format. Each **record** can be thought of as a single document or object that encapsulates a particular set of data, which can be easily stored, queried, and manipulated. **Records** can be created, retrieved, updated, and deleted via our app's user interface or RESTful API, providing you with the flexibility and control you need to manage your data effectively. Using JSON data makes it easy to store and work with your information in a standardized and scalable format. A **record** can either be privately or publicly accessible, depending on its parent [collection](/terminology/collection.md). If a record is not assigned to a specific collection, it is publicly accessible by default. {% hint style="danger" %} **Public** record can be edited by anyone who have the record id. {% 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://docs.myjson.online/terminology/record.md?ask=&goal= ``` `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.