Using Realtime Unified APIs at Truto: Key Considerations
Before you dive into using our Realtime Unified APIs, we would like to bring your attention to a few important considerations. Understanding these will help you use Truto APIs more effectively.
Rate limiting is a crucial aspect to consider when using our APIs. Here at Truto, we rely on real-time data and do not cache it, which means we count on you, the customer, to manage the rate limiting.
What is Rate Limiting?
Rate limiting is a strategy for limiting network traffic. It sets a limit on how often an API client (like a user or a server) can make a request to the APIs within a certain timeframe.
For example, let's say an API can handle 100 requests per minute. If you make more than 100 requests in that minute, the API might stop working because it has been overwhelmed. Since we call data in real time and don't cache it, we rely on you to keep your request rate within the underlying API's limit.
Our Unified APIs provide Data filtering methods to extract some data with unique specifications from a large set of data coming from underlying API. For example, you may want to filter a list of users to only see those who are currently active.
However, the availability of these filters depends on the integration in question. For instance, Salesforce API might allow you to filter users based on their status (active or inactive), so you can use it to find the desired results. If Hubspot API does not support filtering users on basis of this query param i.e. status, in that case this filter will simply be ignored.
To assist you with this, we provide meta routes for every unified API at Truto. These list down all the filters supported for a particular integration, helping you understand how to filter data from that API.