Fetching data

At Quartr, we do our best to provide you with the most accurate and up-to-date data. However, we understand that sometimes things can get a bit tricky. That’s why we’ve put together this page of information to help you navigate the process of fetching data from our API and keeping it in sync with the latest changes.

If you haven’t already, we recommend checking out the authentication guide and the data overview to obtain a API key and understand the data structure before diving into the specifics of fetching data.

​

Datasets

The Quartr API provides access to a variety of datasets that can be purchased individually or as part of a bundle. Each endpoint is designed to provide specific data related to a particular dataset. By keeping the datasets separate, we can ensure that you only pay for the data you need and that the API remains fast and efficient. The events and companies endpoints are available to all customers. These contain metadata that make it easier to work with the other datasets.

Most of the endpoints support the same query parameters, which makes it easy to filter and sort the data. The most common query parameters are company identifiers, date ranges, and pagination. You can find more information about the available query parameters in the API reference.

​

Polling vs Webhooks

The Quartr API supports both polling and webhooks for fetching data. Polling is the process of regularly checking the API for updates, while webhooks allow you to receive real-time notifications when data changes. Polling is a good option if you need to fetch data on a regular basis and can tolerate some delay in data freshness. Webhooks are ideal for applications that require immediate updates, such as live audio or transcript streaming. If you find yourself polling the API more than once a second, we recommend using webhooks instead. This will help reduce the load on our servers and ensure that you receive updates in real-time.

To optimize your data fetching:

• Use the updatedAfter and updatedBefore query parameters to fetch only the data that has changed within a specific time window.
• Use the limit parameter (up to a maximum of 500) to reduce the number of requests needed when retrieving large volumes of data.

When integrating with webhooks, remember to setup a process to handle situations where your data gets out of sync or something fails. This can happen if you miss a webhook event or if the data changes in a way that you didn’t expect. We recommend that you implement a fallback mechanism that allows you to re-fetch the data from the API in case of any issues.

​

Rate limits

Starting December 1, 2025, we will be implementing rate limits to ensure fair access for all users. The limit will initially be set to 50 requests per second.