Data Sources
A data source is where a graph gets its numbers. Before a chart can show anything, you tell Dashboard.PT where the values live and how to read them. This page explains the three ways to feed data into the platform, how field mapping works, and how refresh limits depend on your plan.
Overview
Data can reach Dashboard.PT in three ways: the platform can pull it from a REST API endpoint, you can push it in through a webhook, or you can import a data file by hand. Whichever you use, the final step is the same: you map the fields in the incoming data to the values your graphs plot.
Three ways to feed data
- REST API endpoint — the platform polls a URL you configure and reads its JSON response.
- Webhook — your systems push data into Dashboard.PT as events happen.
- Manual import — you upload a data file for a one-off or occasional load.
Choosing a method
Each method suits a different situation. Use this table to pick the right one before you set a source up.
| Method | Direction | Best for |
|---|---|---|
| REST API | Platform pulls | Data already behind an API you can reach |
| Webhook | Your system pushes | Near real-time events as they happen |
| Manual import | You upload | Historical or one-off data |
REST API endpoints
With a REST source, Dashboard.PT does the work of fetching data for you. You configure a URL and the platform polls it on a refresh interval, reads the JSON response and maps the fields you choose onto your graphs. This is the best fit when your data already lives behind an API you can reach.
| Setting | What it does |
|---|---|
| URL | The endpoint the platform calls to fetch data. |
| HTTP method | Usually GET, or POST when the endpoint expects a request body. |
| Headers | Custom headers sent with each request, such as content type. |
| Authentication | A token, API key or basic auth so the endpoint accepts the call. |
Webhooks
A webhook flips the direction: instead of the platform pulling data, your own systems push data into Dashboard.PT as things happen. You get a unique webhook URL and your application sends values to it, so the graph updates the moment an event occurs, without waiting for a polling cycle. This is ideal for near real-time signals like a sale being made or a job finishing.
Manual import
When your data is not connected to anything, you can import it by hand. Upload a data file and the values are loaded into the graph in one go. This suits historical data, occasional updates or a quick way to get started before you wire up an API or webhook.
Field mapping
Field mapping is how you tell a graph which values from the source actually matter. A response often carries many fields; mapping lets you point at the one that becomes the plotted series and the one used for labels or the time axis, ignoring the rest.
- Open the data source and look at a sample of its response.
- Select the field that holds the value to plot (for example value or count).
- Select the field used for the label or timestamp (for example timestamp or name).
- Save the mapping. From then on, every refresh reads exactly those fields.
Refresh interval limits
For REST sources, the refresh interval decides how often the platform polls the endpoint. Just as with graphs, the shortest intervals are reserved for higher plans: your plan sets the minimum interval you can choose, so a lower plan polls less frequently. Webhook and manual sources are not polled, so this limit does not apply to them, though webhook throughput is still governed by your plan.
Note: For programmatic or custom integrations you can also drive data sources through the platform's REST API using API Keys. See the REST API Reference for the available endpoints and how to authenticate.
Note: Never put secrets in the URL. Keep tokens and API keys in the Authentication or Headers settings, where they are handled securely, rather than in the query string.
Want to try it? The free plan has no time limit.
Create a free account