Sync a data source on a data feed
Starts a fetch of a sql or api source, the same as the Sync button on the Sources page, and returns the new run. The run collects asynchronously; follow it with GET /data_feeds/{data_feed_friendly_id}/runs/{run_friendly_id}. Requires the write:data_feed token scope.
- A sync doesn’t wait for
max_fetches_per_hourspacing or a provider’sRetry-After, and replaces any follow-up fetch the source was waiting to make. Forerror_code: rate_limited, wait fornext_fetch_atif set: the source retries automatically. If it is null and the source’sdaily_fetchis on, a newer run of the source has already followed this one; ifdaily_fetchis off, nothing retries automatically, so sync or retry only after the provider’s limit resets. Another rate-limited run can extend the wait. - With
daily_fetchon, a window cut short bymax_window_secondsis followed by the next window, as that field describes. Withdaily_fetchoff, each call fetches once.
A 409 clears on its own, so try again later; a 422 needs the source or data feed fixed first. Each 409 and 422 error carries a code.
Path Parameters
Response
Fetch started; returns the new run.
A data feed run.
Earliest time the automatic retry or next capped window is due, derived from current source settings. Null when nothing follows this run, including when a newer run exists or daily_fetch is off. This does not confirm a job is queued. A past time can mean the follow-up is queued, delayed or missed; the next daily fetch can recover it.