Search HubSpot CRM objects using the Search API with filters and pagination
domain: developers.hubspot.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to /crm/v3/objects/{objectType}/search with a JSON body containing filterGroups, sorts, properties, limit, and after (pagination cursor)
Each filterGroup contains a filters array where each filter has propertyName, operator (e.g., EQ, CONTAINS_TOKEN, GT), and value
The response includes a results array and a paging.next.after cursor — pass this cursor as after in the next request to get the next page
Specify only the properties you need in the properties array to reduce response payload size
Combine multiple filterGroups with an implicit OR; filters within the same filterGroup are ANDed
Known gotchas
The Search API returns a maximum of 10,000 records total across all pages for a given query — for larger exports use the batch read or list API instead
Search results reflect a search index that may lag real-time data by a short delay — for strict consistency, fetch the record directly by ID after a recent write
Rate limits on the search endpoint are lower than on standard CRM endpoints; high-frequency search polling will trigger 429 errors quickly
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?