Skip to main content
The Explorer API does not push webhooks to exchange keys. You pull: tokenomics via its feed cursor, monitoring via its windowed feed, notifications via the inbox. This page is the recommended poll pattern.

Poll the tokenomics feed

Persist nextCursor after each run. A since poll returns only newer revisions — empty polls are cheap.
Pseudocode
  • Always send since, never re-read the backlog once you have a cursor.
  • hasMore with since means keep polling immediately — the window caught up faster than the page size.
  • Backfill history once with page tokens, then switch to cursor polling forever.

Poll monitoring changes

There’s no cursor on /me/monitoring/changes — instead it’s a rolling window plus a seen marker:
newOnly=true returns only changes newer than your last seen marker — the built-in incremental read. For scheduled sweeps, pass days sized to your poll interval plus margin (e.g. days=1 hourly is wasteful; days=7 daily gives overlap).

Poll notifications

GET /me/notifications?unread=true is the inbox check — read it at the cadence you alert on, and mark-read in the explorer UI.

Stay inside the budget

At the default 120 req/minute you can poll every second, but a 15–60 s interval is plenty for monitoring cadence.

FAQ

Not for key access today. If you need push, ask Bluprynt — otherwise poll with since/newOnly, which is near-real-time for monitoring cadences.
For incident-level alerting, 15–60 s on since + newOnly. For daily sweeps, one days=7 pull per day.