Add chains to a sync
Start syncing more chains. With the sync’s backfill on, the added chains’ history is backfilled for every watched wallet, and the other chains are not read again; this answers 409 while a backfill job is still running.
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
Goldsky chain slugs or dataset prefixes.
11Response
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.