Why?

When querying our API for large datasets, there was a chance that some records were being missed out between calls. 

This made it difficult for you to retrieve all your data using our API to, for example, update your internal CRM.

Clients affected

  • All clients using our GET API endpoints.

What’s new?

We have made two changes to the behaviour of our API to reduce the risk of records being missed out:

  • All API endpoints will return results sorted by their ID in ascending order by default unless the 'orderby=timestamp_update' query parameter is specified.
  • The sorting direction of the `timestamp_update` query parameter has changed from descending to ascending order.

N.B. Using the timestamp_update query parameter for large data sets may result in record duplication.