> For the complete documentation index, see [llms.txt](https://docs.validere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.validere.com/guides/api.md). # API Welcome to Validere's API, a RESTful interface designed for efficiently integration data between client data sources/sinks and the platform {% hint style="info" %} `https://api.validere.io` {% endhint %} The API is organized around REST and has resource-oriented routes, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, verbs and versioning. ## Use Case The API is ideal for clients looking to integrate their data with Validere’s platform. It supports various data formats and is optimized for high-frequency, medium-latency data transfers. ### Using the API * **Push Data**: Send data directly to the Validere platform and any shape to best accomodate source systems and to minimize data transformations * **Retrieve Data**: Access asset configuration, operational and emission data both submitted to and computed within the platform * **Transaction Details**: Get insights about your data ingestion transactions --- # 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.validere.com/guides/api.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.