Construct a SavedSearchAdvanced SOAP request referencing the saved search internal ID in the savedSearchId field and post it to the SOAP endpoint
Set searchPreferences.pageSize in the SOAP header to control records per page; page size has platform-enforced upper bounds
The initial search response contains a searchId and a pageIndex; use searchMoreWithId with the returned searchId and incrementing pageIndex values to retrieve subsequent pages
Detect the end of results when the response totalRecords count divided by pageSize equals or is less than the current pageIndex
Handle SOAP faults separately from application-level errors in the search response's status field
Known gotchas
The searchId is session-scoped and expires with the SOAP session; if your session times out mid-pagination, you must restart the search from the beginning
Saved search column order in the SOAP response matches the column definitions on the saved search, not the order of fields in the SOAP schema — map by column index or label, not by field name
Modifying the saved search definition in the UI while a pagination loop is in progress can cause inconsistent results or errors on subsequent searchMoreWithId calls
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp