Backfill a sync
Update the sync, then read history again from the start: for every watched wallet, or for the one address names. Runs even with the sync’s backfill off. A single-wallet backfill answers 409 while the sync’s backfill job is still running, so it never cuts one short.
Authorizations
API token generated from the Goldsky Dashboard. Pass as: Authorization: Bearer
Path Parameters
The feed's theme, e.g. wallets.
The feed's dataset, e.g. balances or transfers.
The sync's name.
1Body
Backfill only this watched wallet. Leave out to backfill every watched wallet.
1Response
Default Response
The chains the sync covers, by Goldsky chain slug.
Whether each wallet's history is backfilled when it is added, and an added chain's history for every wallet.
The secret holding the destination database's credentials, or a webhook's auth headers.
The compose app holding the sync's watched wallets and tokens, and running its tasks.
The pipeline that streams new rows.
The job that backfills history, once the sync has backfilled at least once.