17 September 2026 When you read related data through the Engage API, the API can now filter and sort the records for you. Instead of retrieving every record stored under a key and narrowing the result in your own application, you ask for exactly the records you need, in the order you need them.
A single contact can have hundreds of stored records, for example purchases, orders or interactions. In most cases only a few of them are relevant to the request at hand.
Key Benefits
Smaller responses and less data transferred, especially for contacts with long histories.
Less code on your side, because filtering and sorting no longer have to happen after the response arrives.
Cleaner input for AI agents and automated workflows, which work better with a focused result set than with a large unfiltered one.
No change to existing integrations. The new parameters are optional, and requests without them behave exactly as before.
How does it work?
The getRecordsByKey endpoint accepts three optional parameters: one for the filter, one for the field to sort by and one for the sort direction. A filter can combine several conditions, compare numbers and dates, and search for text within a field.
For the full syntax, including all supported operators and worked examples, see Filtering and Sorting Related Data Records.
Availability
This feature is available now.