> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/faqs/what-data-is-available.md).
# What data is available?
Have Questions? Reach out!
There are two ways to review which fields are available in a connector:
## Via the app connection
Once [you've connected your app](/middle-docs/product/accounts/connect-or-edit-an-app-connection.md), you can click the app and see all of the different record types available to sync. If you click [**Records**](/middle-docs/product/accounts/sync/stored-records.md) to the right of the record type name, you'll be able to see the available fields at the top of the page. If you've already synced data into that record type you'll be able to see examples of real data.
{% content-ref url="/pages/kRFRsNLHwKShFTjDEqCj" %}
[Stored records](/middle-docs/product/accounts/sync/stored-records.md)
{% endcontent-ref %}
Reviewing the available fields in a lead record type
## Via the app development portal
Click **Apps** at the top of your Middle dashboard and then search for the app you'd like to review. In the left-hand menu, you'll see a section for [record types](/middle-docs/product/apps/sync-records.md). If you click on a record type you'd be able to see and edit the configured fields.
{% content-ref url="/pages/tUGlpSXCqGexItwPwfV4" %}
[Apps](/middle-docs/product/apps.md)
{% endcontent-ref %}
{% hint style="warning" %}
The app development portal is only available to ENTERPRISE customers
{% endhint %}
## API documentation
You can also review available data by looking at the API documentation for the respective app.
{% hint style="info" %}
The best way to see which endpoints Middle is using is by reviewing the [sync code](/middle-docs/product/apps/sync-records.md) in the app development portal
{% endhint %}
{% hint style="success" %}
If you see any fields missing from Middle's syncs feel free to add them yourself via the [app development portal](/middle-docs/product/apps.md) or reach out to the Middle integration team at .
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.middle.app/middle-docs/faqs/what-data-is-available.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.
