Hi HubSpot team,<\/P>
I’ve been integrating with the Events API v3 (\/events\/v3\/events\/) and ran into several issues that either aren’t documented or are documented incorrectly. Sharing them here for visibility.<\/P>
\u00a0<\/P>
Pagination doesn’t work correctly. The API returns a valid paging.next.after token, but subsequent pages return almost nothing.<\/P>
Without eventType filter:<\/STRONG> With eventType filter:<\/STRONG> However, setting limit=2147483647\u00a0(max signed\u00a0<\/SPAN>32-bit int<\/SPAN>) returns 160+ results in a single response. The data exists, pagination just doesn’t traverse it.<\/P> \u00a0<\/P> The docs say:<\/P> This implies pagination, but setting a large limit value returns everything in one request. The parameter controls total results, not page size.<\/P> This is actually the only working approach given bug #1, but the documentation is misleading.<\/P> \u00a0<\/P> Documentation states:<\/P> Actual behavior: passing sort=ASCENDING or sort=DESCENDING returns:<\/P>{“status”:”error”,”message”:”Only a single sort field ‘occurredAt’ is supported”} The correct format is sort=occurredAt (ascending) or sort=-occurredAt (descending). Standard REST convention with minus prefix for descending, but not what’s documented.<\/P> \u00a0<\/P> Documentation states you can filter by event instance ID:<\/P> When I try this:<\/P>{ The linked URL is internal (product.hubteam.com), not accessible to developers. There’s no public documentation on the “idempotency index” or how to opt event types into it. Standard events like e_visited_page don’t support this filter at all.<\/P> \u00a0<\/P> Environment:<\/STRONG> \u00a0<\/P> Would appreciate clarification on these behaviors and updates to the documentation. Happy to provide more details or test fixes.<\/P> Thanks!<\/P><\/p>\n","protected":false},"excerpt":{"rendered":" Hi HubSpot team,I’ve been integrating with the Events API v3 (\/events\/v3\/events\/) and ran into several issues that either aren’t documented or are documented incorrectly. Sharing them here for visibility.\u00a01. Pagination is brokenPagination doesn’t work correctly. The API returns a valid paging.next.after token, but subsequent pages return almost nothing.Without eventType filter:– Page 1: 100 results, valid […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"_links":{"self":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/2079"}],"collection":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/comments?post=2079"}],"version-history":[{"count":1,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/2079\/revisions"}],"predecessor-version":[{"id":2080,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/2079\/revisions\/2080"}],"wp:attachment":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/media?parent=2079"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/categories?post=2079"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/tags?post=2079"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
– Page 1: 100 results, valid after token
– Page 2: 1 result, no more paging
– Total via pagination: 101<\/P>
– Page 1: 100 results, valid after token
– Page 2: 0 results, no more paging
– Total via pagination: 100<\/P>2. limit parameter doesn’t work as documented<\/H2>
limit (integer) – The maximum number of results to display per page<\/STRONG>.<\/BLOCKQUOTE>
3. sort parameter format is wrong in docs<\/H2>
sort (string[]) – Sort direction based on the timestamp of the event instance, ASCENDING or DESCENDING<\/STRONG>.<\/BLOCKQUOTE>
4. id parameter has undocumented requirements<\/H2>
id (string[]) – ID of an event instance. IDs are 1:1 with event instances.<\/BLOCKQUOTE>
\n “status”: “error”,
\n “message”: “Queries using idempotency IDs require the event type 4-96000 be opted into the idempotency index. Idempotency index docs: https:\/\/product.hubteam.com\/docs\/hubspot-framework\/unified-events\/events\/indexes\/idempotency.html”
\n}
– API: Events v3 (\/events\/v3\/events\/)
– Account: Enterprise tier
– Auth: Private app with static token<\/P>