AI API Finder
Describe the data you want and Flitch finds a public REST API for it, then maps its endpoints.
Describe the data you want in plain language. Flitch searches the web for public REST APIs, maps their endpoints, and lets you preview and connect them as datasets. For public data where you do not already know the API.
Like any integration, this connects a data source first. You find and connect a public API as a dataset, then build dashboards on it in plain language.
Connect
Open the finder
Go to Data → Add → AI API finder.
Describe what you want
Type what data you are after, for example "live weather for a city" or "daily currency exchange rates". Flitch searches for public APIs and maps their endpoints.
Preview an endpoint
Each result lists endpoints with example parameters. Edit the parameters if you like, then Preview to see the live response before committing.
Add a key if needed
Many public APIs are open. If one needs a key, paste it in. Flitch sends it the way that API expects, as a bearer token, a header, or a query parameter.
Connect
Connect the endpoint and it becomes a dataset.
Field mapping
The endpoint response must be a JSON array, or an object with an array under a top level field ({ data: [...] }, { results: [...] }, etc.). Each record becomes a row; nested fields flatten with dot notation.
Refresh
An API-backed dataset can refresh on a schedule, so Flitch re-queries the endpoint and dashboards stay current. See Refresh.
Some public APIs block requests from server networks (bot or firewall protection). When that happens Flitch marks the endpoint as blocked in the preview, so you know before connecting.
Troubleshooting
Needs a key. The endpoint returned an auth error. Add the API key and choose where it goes (bearer, header, or query parameter) if the default does not work.
Blocked by the API. The API is refusing requests from Flitch's servers, not a problem with your settings. It may only work with an official key, or may not be reachable from our hosting.
No array of records found. The response is JSON but the records array was not located. Preview the endpoint and adjust the path if needed.