> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/soccer/objects.md). # Objects JSON (JavaScript Object Notation) is a widely used data interchange format that is lightweight and easy to read. It represents data in a structured manner using key-value pairs. Within JSON, objects are one of the fundamental components for organizing and representing data. A JSON object is enclosed within curly braces {} and consists of a collection of key-value pairs. The keys are strings that provide a label or identifier for the corresponding values. The values can be of various types, including strings, numbers, booleans, arrays, or even nested objects. JSON objects enable the organization and storage of complex data structures in a hierarchical format. They offer flexibility, allowing developers to represent and manipulate data in a concise and human-readable manner. JSON objects are commonly used for transmitting and storing data in web APIs, configuration files, and various data exchange scenarios. In summary, JSON objects serve as containers for data, providing a standardized and versatile format for representing structured information in a lightweight and easily understandable way. --- # 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.sportradar.com/soccer/objects.md?ask=&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.