> For the complete documentation index, see [llms.txt](https://developer.ivvy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ivvy.com/getting-started/interpreting-the-response/dates.md). # Dates Responses from the iVvy API may contain dates. In all cases (unless otherwise stated in documentation for the specific action) the dates are in Universal Coordinated Time (UTC). Care must be taken when using or displaying these dates to ensure they: a) maintain their UTC time zone for communication with the API, and; b) represented in the appropriate time zone for users utilizing the date. Dates may be represented as a string which must be parsed appropriately if it is to be used. Where possible any dates will be converted to the[ iVvy Timestamp Format](/development-reference/timestamp-format.md), which is a simple to understand text format to represent a specific point in time to the second. --- # 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://developer.ivvy.com/getting-started/interpreting-the-response/dates.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.