Pagination

​

Feed pagination

{
  "items": [ "…" ],
  "hasMore": true,
  "nextCursor": "tfc1_c2VxOjE4MzA5MjE",
  "nextPage": "tfp1_cGFnZTo…",
  "order": "priority"
}

curl -s "https://explorer-api.bluprynt.com/tokenomics/changes?limit=50" \
  -H "Authorization: Bearer bx_live_…"

# Newer revisions later — poll the cursor
curl -s "https://explorer-api.bluprynt.com/tokenomics/changes?since=tfc1_c2VxOjE4MzA5MjE" \
  -H "Authorization: Bearer bx_live_…"

# Older backlog — pass the nextPage token back unchanged
curl -s "https://explorer-api.bluprynt.com/tokenomics/changes?page=tfp1_cGFnZTo…&limit=50" \
  -H "Authorization: Bearer bx_live_…"

​

Page caps

• Tokenomics feeds cap limit at 200 per page (default 50).
• Monitoring changes cap at 200 items per response; when the window holds more, the response sets truncated: true. Narrow with days, category, item, or materiality until truncated clears — the rest still exists server-side.
• Watchlist items come back complete (your whole list, up to your key’s limit).
• /me/notifications returns your inbox in one read; unread=true filters to unread only.

​

Cursor rules

• since and page are opaque. Never construct them — always take them from nextCursor/nextPage.
• A page token is bound to its filters by a fingerprint: change the filter set and reuse the token → 400 invalid_page. Keep filters identical while paging.
• An invalid since returns 400 invalid_cursor; a bad page returns 400 invalid_page.
• Persist nextCursor between polls. A later catch-up call fetches exactly what arrived since, without re-reading backlog.

​

FAQ

​

Related

• Tokenomics changes — filters and fields
• Polling guidance — the recommended loop