1. Read the first page
Inspect the current contract and price:since timestamp in the first request.
since filters discovery time, not the funding announcement date. The feed
has no company, industry, round-stage, or source filter.
2. Consume every cursor page
Persist each successful page before continuing. Whendata.has_more is true,
pass that response’s exact data.next_cursor as cursor:
has_more is false. Retain failed pages as unfinished work;
a successful first page does not complete the read.
3. Advance the checkpoint after processing
Store the original discovery-time boundary, successful pages, and next cursor. Useupdate_id to deduplicate discoveries across repeated or overlapping reads.
since is inclusive, so the boundary can return an already processed update.
Advance the saved discovery-time checkpoint only after every page has been
stored and processed. Preserve it when any page fails. Funding announcements
and response times are not substitutes for the discovery boundary.
The feed creates neither a schedule nor a Monitor. For recurrence, own the
checkpoint and retry policy in a Play or scheduler.
Choose the interval for your review needs; no publication cadence is promised.
Use Review account signals to
qualify the retrieved events before account actions.
Call the API
HTTP requests and cursor continuation
HTTP requests and cursor continuation
Use a workspace-scoped API key from a trusted server or worker. Do not expose
the key in browser code.For the next page, persist the prior response and build the request from its
cursor. Only run this when the prior response has
data.has_more: true.