Skip to main content
POST
Trigger a wallet sync (incremental or custom period)

Path Parameters

id
string
required

Wallet ID

Example:

"1"

Query Parameters

orgId
string
required

Organization ID. Use GET /v1/companies to discover available org/company pairs.

Example:

"1"

companyId
string
required

Company ID. Use GET /v1/companies to discover available companies and their access levels.

Example:

"1"

Body

application/json
dateFrom
integer

Start of a custom sync window (unix seconds). Use this to backfill a period that was never imported (e.g. the wallet only holds 2026 data and 2024/2025 are missing). Omit the body entirely for the default incremental sync.

Required range: x > 0
Example:

1704067200

dateTo
integer

End of a custom sync window (unix seconds). Requires dateFrom. Must be <= now for a backfill that avoids overlapping already-imported data. Not supported on Solana, Cardano, Bitcoin, or Tron wallets (their providers paginate from the chain tip); on Solana pass toHash instead.

Required range: x > 0
Example:

1735689599

toHash
string

Solana wallets only. A transaction signature used as the upper boundary: the sync starts at this transaction and walks BACKWARDS to dateFrom, so only transactions older than this hash are imported. Pass the signature of the oldest transaction already imported for this wallet so the backfill stops exactly where the existing data begins. Requires dateFrom.

Required string length: 1 - 120

Response

Sync triggered successfully

success
enum<boolean>
required
Available options:
true
data
object
required
Last modified on July 10, 2026