Update a sync
Redeploy the sync with Goldsky’s latest pipeline and task templates. A finished backfill job is re-applied for the watched wallets and resumes from its checkpoints, so no history is read again; a running one is left to finish. Answers 409 while the sync is being set up or updated, or is paused.
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.
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.