> For the complete documentation index, see [llms.txt](https://docs.thryve.health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thryve.health/thryve-product-overview/access.md). # Access When your user has connected their data source, we will immediately start retrieving your user's data, making sure you can start working with it within seconds of the data source connection. Thryve's data processing and storage engine will collect the data from all kinds of data sources, harmonize and normalize it according to the Thryve data type definitions and provision it to you via our API endpoints. The subsequent pages will introduce you to all the types and dimensions available as well as give you an overview of when data will be available and how historic data (prior to user connection) can be retrieved and configured. If you want to understand the technical implementation to access, you can directly jump into the following pages: * [Receiving data updates via webhook notifications](/receive-updates-via-webhooks/notifications.md) --- # 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.thryve.health/thryve-product-overview/access.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.