Paginate an address history
Full address history can span thousands of transactions, so you need reliable paging. List endpoints accept limit and offset and echo them back, giving deterministic pages you can resume. Deep history comes from archive nodes without extra setup.
- An API key (sk_live_...) with read access.
- An address on eth, btc or tron.
1Fetch the first page
Start with offset 0 and a fixed limit. Keep the limit constant across the whole scan so offsets line up cleanly.
curl "https://api.1st-node.com/v1/data/eth/address/0x53d2...9a1f/transfers?limit=100&offset=0" \ -H "Authorization: Bearer sk_live_..."
2Use the echoed limit and offset
The response echoes limit and offset. Compute the next offset from these values rather than tracking state locally, which avoids drift if a call is retried.
> { "limit": 100, "offset": 0, "items": [ /* up to 100 items */ ] }3Loop until the page is short
Advance offset by limit each iteration. When items comes back shorter than limit, you have reached the end of the history.
curl "https://api.1st-node.com/v1/data/eth/address/0x53d2...9a1f/transfers?limit=100&offset=200" \ -H "Authorization: Bearer sk_live_..."
Частые вопросы
Is offset paging stable if new transactions arrive?
Order is by block, so already-confirmed pages stay stable. New activity appends at the head; scan oldest-first or refetch page 0 to pick up fresh items.
Does paging deep into history cost extra?
Deep ranges are archive-depth (C2) and served from our own archive nodes. You pay per call, so a long backfill costs per request, not per server.
Читать дальше
Пополнили, получили ключ, запустили.
Полное самообслуживание. Оплата криптой или картой. Тарификация в кредитах — тяжёлые примитивы дороже, простые дёшевы.
Получить API-ключ