Key Features
Of course each application connection will have it's own unique characteristics that we are always ready to implement, however we have already standardized the more common, greater approaches.
Caching
In order to to speed up our API's responsiveness, efficiency and to reduce load on both sides of the parties, there is caching implemented. This usually stores recently queried data for 4 hours. This means that on same requests, there wont be a need for unnecessary duplicated calls, and query speeds will be much higher this way.
Quotas
Although our middleware is more than capable to deliver gigantic queries, it would be unwise to let every application do that. To counter this, quotas are implemented to limit the amount of data, that can be requested in amounts of time.
Pagination
When working with data like ours, it is common to receive thousands of entries per API call. However this can be troublesome to manage and usually causes excess traffic and load both on the server's and client's side.
To tackle this, we have pagination implemented. After showing the first 2000 entries, the call will return with 2 new parameters (nextRunID, nextRunGuid) that if inserted in the header, and calling the API again with the same parameters, will point to the next 2000 entries. This can be repeated over and over. If the call reaches the last entry, the 2 parameters will be set to NULL values, indicating that no more entries are available.
Delta load
If a consumer decides that they have no need for real time data, they can request to get the only the Deltas in specified intervals. The Delta load will contain the changes that are the most relevant until the interval point. This ensures that the data received is up to date, and minimalizes the load for both parties.
Want to know more?
Check out our different environments, or check out how we authenticate API calls!