Cache snapshot
Webhooks can be configured to automatically build a cache snapshot when they fire, so your integration receives everything it needs to begin paging immediately — without building the cache manually. This works for any webhook source, including tables (table) and price columns (pepe).
How it works
WhenincludeDataCacheKey is enabled on a webhook, each time the webhook fires it:
- Builds a snapshot that freezes the set of matching rows and their order for the configured source object.
- Delivers a webhook callback with the cache metadata instead of raw row data.
cacheKey, the row selection and ordering are stable, but the column values returned reflect the current state of the data at the time each page is fetched.
Webhook notification payload
In addition to the standard webhook fields (eventType, eventTime, eventId, source, sourceObject), the body includes:
Use
source and sourceObject from the payload to determine which data endpoint to call when fetching pages.
Example payload — table source
Example payload — price column source
Fetching data after a webhook fires
UsecacheKey from the webhook payload and call the appropriate data endpoint based on source:
Table source
Price column source
Page for each subsequent page until you have consumed totalPages pages.