Navigator Agreements API - Is Combining $search and $filter Supported?

Hi HariGopal, I can confirm that these query params cannot currently be combined in a single call. I apologize, but I don’t have any insight as to when it will be supported. I will also update the developer documentation to make this explicit.

To work around this limitation, you can use sequential GET calls with separate query params, using $search first to get the IDs of the agreements you want, then making a $filter call to narrow on the fields you want.

For example, making a GET /agreements?$search=”data processing” call, and parsing/saving the IDs from the response. Then making a GET /agreements?$filter=id in (‘your-returned-id-1’, ‘your-returned-id-2’) and status eq ‘ACTIVE’

Thank you for the clarification and suggested workaround.

We have a follow-up question regarding pagination and performance.

In our application, the Agreements List API supports paging, and users can combine search and filters while browsing large result sets. If we implement the suggested approach of performing a $search request first and then applying a $filter request using the returned agreement IDs, we may need to retrieve and process a very large number of search results before filtering can be applied.

For example:

• A search term such as "Agreement" or "Contract" may return thousands of agreements.

• To apply a status filter (e.g., ACTIVE) or agreement type filter, we would first need to retrieve all matching search results across multiple pages.

• We would then need to collect all agreement IDs and issue additional filtered requests.

• This could introduce significant latency, increased API calls, and scalability concerns for large customer datasets.

We would appreciate any guidance on best practices for implementing efficient search and filtering at scale.