Query API
EventBunker supports HTTP POST requests with query api key and JSON data specifying the query elements to analyze your event data and return a JSON or an Embeddable Chart Html as response. Query response time is kept under 1 second for %99 of the requests in EventBunker so that you do not have to think about performance, caching or other factors while creating your user(customer) facing analytics dashboards. We scale up the api and underlying database automatically to keep performance consistent.
Query Api has multiple elements, such as filters, limit, orderby, calculation type, groupby, timeperiod and timezone and more. Using combination of these elements, you will be creating a query request, similar to how you would write a SQL query to select relevant data with filters and desired calculations, like min, max, avg, count, unique, etc.. You will find detailed documentation for each element in this section together with examples to help you.
EventBunker supports multiple projects and api keys under one account. For querying data, you will have access to a single Project's data, this means you can not currently combine multiple projects' data in one query request. We use your query api key to determine project id, so QUERY api keys are mandatory in request header for http post method and in query parameter for http get requests.
Projects are logical separation of collected event data and queries. Which means that you can not access a project's data from another project using api keys, so think about query use-cases before designing data ingestion.
We suggest using separate projects for separate applications, mobile apps, websites, etc.. where you do not need to combine data for single view of analytics.
You will see billed query request counts by project in our web application for billing purposes.
There is an additional feature in query api keys if a customer_identifier attached to api key during creation, please read more at How to Use Api Keys
Query Request Elements
In this section you will find out how to create a query request using SQL like concepts (select, where, order by, group by) with JSON elements that we defined for ease of use with rest apis. This implementation is very similar in many apis where you can not just pass a sql query directly. Also this way we keep things simple for you as an end user.
Continue reading at Query Request Elements
Common Analytical Query Examples
To speed up your development time even further, we have created example queries for many common use-cases, you can simply copy paste and then change parameters' values and start using these examples.
We also talk about complex query types in this section. Examples will be added to documentation constantly to show what scenarios are possible using EventBunker Analytics API.
Continue reading at Query Examples
Looking for more?
Please contact us by email if you have a tracking use-case which you think that is not covered in EventBunker. All kinds of analytical queries are possible with custom development per use-case.