In this section you will find Tinybird Analytics-related terms and their definitions.
When you import data into Tinybird Analytics it goes into a Data Source. It is where you store your data; you can append more data to each of them as well as perform SQL queries against them.
Data Sources can be managed through the Console UI or the Data Sources API.
Pipes are the most important concept in Tinybird Analytics. They are a sequence of one or more SQL queries (transformations) that you can:
apply to one or more Data Sources,
apply to the result of other pipes, and
publish as an API endpoint that anyone with permissions can then query through HTTP in JSON or CSV formats.
Think of Pipes as data transformations. You can transform your data through Pipes and the result is a resource you can query: if you have a pipe called
test_pipe, you can query it like
SELECT count() from test_pipe. If
test_pipe has three transformations (three different SQL queries), Tinybird will apply all those queries in sequence when you use it.
Access to Tinybird Analytics’s API requires an Auth Token that connects API requests to your account with special permissions. Once you get access to the platform, a default admin Auth Token gets created for you, but you can also create and manage additional tokens through Tinybird’s UI or using the Auth token API.
When creating a new Auth token, you have the option of setting:
one or many scopes (
different permissions (
"City='Madrid'") through which you can restrict access to specific subsets of your Data Sources or pipes.
Our web services support Cross-Origin Requests with no domain restrictions. To support Internet Explorer 8 and 9, use a library that falls back to XDomainRequest, like corslite.