Skip to main content
Trigger transaction synchronization for an address, bypassing the 10-minute cache to force an immediate update.
Cost: 1 credit + 1 credit per 250 transactions indexed
Index Limit — Addresses with more than 100,000 transactions are not indexed. Contact support for assistance.
Interactive Playground: Test this endpoint in the API Playground. Get your API key at data.octav.fi

Endpoint

Request Body

addresses
array
required
Array of addresses to sync (currently supports 1 address)

Example


Response

Returns a string indicating sync status:
  • "Address is syncing" - Synchronization started
  • "Address already syncing" - Address is currently syncing

Cost Breakdown

1 credit per sync request
1 credit per 250 transactions indexed
  • Only new transactions since last sync are indexed
  • Transactions are indexed permanently (one-time cost)
  • Subsequent syncs only pay for new transactions

Example Costs

Address with 10,000 transactions:
  • API call: 1 credit
  • Indexing: 40 credits (10,000 ÷ 250)
  • Total: 41 credits ($1.03)

Use Cases

Force immediate transaction sync:

Best Practices

Use the Status endpoint to check if a sync is needed before triggering oneAvoid unnecessary sync costs by checking transactionsLastSync timestamp
If you receive “Address already syncing”, wait for the current sync to completeTypical sync time: 5-30 seconds depending on transaction count
First-time syncs can be expensive for addresses with many transactionsRegular syncs are cheap as only new transactions are indexed

Status

Check when last synced

Transactions

Query synced transactions