> ## Documentation Index
> Fetch the complete documentation index at: https://docs.communityhub.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Data Sources to Data Hub

> How data sources work in Data Hub — the categories of source, what each documentation status means, credential handling, and where to go next.

Data Hub receives data from **data sources** — dataloggers, building automation systems, and public APIs. This section has one page per source; this overview explains how sources work in general, what each source's documentation status means, and how credentials are handled across all of them. Use the sidebar to open the page for a specific source.

## Categories of data source

<CardGroup cols={2}>
  <Card title="Environmental & Weather APIs" icon="cloud-sun">
    Public APIs providing air quality, weather, and regional observational data.
  </Card>

  <Card title="Building & Energy Systems" icon="building">
    Building automation systems and dataloggers that push metered readings from a facility.
  </Card>

  <Card title="Generic Ingestion" icon="file-csv">
    A file-upload endpoint that accepts data from any source able to produce a properly formatted file.
  </Card>

  <Card title="In development" icon="flask">
    Native IoT integrations still in the draft-spec stage and not yet usable.
  </Card>
</CardGroup>

## Documentation status

Each data source page is documented at one of four levels, shown in a callout at the top of the page:

| Status                      | Meaning                                                                                            |
| --------------------------- | -------------------------------------------------------------------------------------------------- |
| **Full setup**              | Device/account configuration steps plus the upload endpoint or API detail.                         |
| **Upstream reference only** | Links to the public API; how to register it as a data source inside Data Hub isn't written up yet. |
| **Not yet documented**      | Nothing has been written; contact the Data Hub team.                                               |
| **Draft spec**              | An architecture proposal for a source that isn't built yet; not a usable setup guide.              |

## Credential handling, across every data source

<Warning>
  Never share upload tokens, API keys, or device login credentials in plain text over email, chat, or support tickets. If you suspect a credential has been exposed, rotate it immediately and notify the Data Hub team.
</Warning>

Credentials are never logged and never displayed again after initial entry. Different sources use different credential models — an upload token, OAuth-style credentials, a bearer token, or a device-side login that Data Hub never sees. See each source's own page for specifics.

## Troubleshooting

<Accordion title="My data source isn't appearing in Data Hub after setup">
  Many device-based sources require the Data Hub team to manually assign your logger's serial number to your organization before data appears. Confirm you've sent your serial number after completing device-side setup.
</Accordion>

<Accordion title="Upload requests are failing">
  Check that you're using your organization's own subdomain in the upload URL (not a placeholder or another organization's subdomain), that you're using the protocol your source's page specifies, and that any required token or header is current and correctly formatted.
</Accordion>

## Next steps

Once a data source is connected and reporting variables:

* [**Polling Intervals**](/guides/scheduling-syncs) — whether that source has a configurable pull interval, and how data-reception status is surfaced per variable.
* [**Derived Variables**](/guides/transforming-data) — calculate new metrics (e.g. combining two variables from different sources) from a formula rather than a data source.