REST v2 - List Endpoints - Ability to Order by the Last Updated Time

API Q&A
1

@OmarAlmonte - Please add the following gap to the issue tracker.

In all the List Endpoints there is no way you can sort the list by the Last Updated (Modification) Time.

This currently can be done in the XML-RPC and is useful when syncing the API data so that you can get the latest updated data first, without having to going through all the records to determine things.

Affiliates, Contacts, Opportunities, Orders, Notes, etc.

2

Thanks for the feedback! I’ll add Contacts, Opportunities, Orders, Notes, and Tasks to the tracker. We don’t currently have it available for affiliates in XML-RPC, so that will need to be evaluated. I’ll update you as soon as I have more information.

3

Hi @Pav,

Just a quick update on this, the Orders list endpoint in REST v2 now supports ordering by modification time, allowing you to retrieve the most recently updated orders first, similar to what was available in XML-RPC.

Additionally, this capability is also available for Products, using last_updated_time, which enables the same pattern for incremental syncs on that entity as well.

You can find the relevant documentation here:

Thanks again for highlighting this use case—it’s been helpful in closing the gap with XML-RPC behavior.

4

Hi @Pav,

Just a quick update on this, this capability is now also available for affiliates, subscriptions, contacts, notes, tasks, tags and opportunities in the REST v2 API. Both endpoints now support ordering by modification time, enabling you to retrieve the most recently updated records first and follow the same incremental sync pattern.

This helps further close the gap with the behavior previously available in XML-RPC.

You can find more details in the REST API docs:

Thanks again for highlighting this use case, it’s been very helpful in driving these improvements.