Skip to main content
POST /api/v2/buyer/advertisers/{advertiserId}/catalogs/{catalogId}/refresh Manually re-fetches a catalog’s stored URL feed, creates a new catalog version when the data changed, and — when asked — executes activation jobs from the active transform. Use it to pull the latest feed on demand between scheduled syncs.
Refresh only applies to catalogs backed by a feed url. A catalog synced with inline items has no stored feed to re-fetch — push new data with sync catalogs instead.

Request

curl

Parameters

Response

  • catalog — the sync result, with action created, updated, unchanged, failed, or deleted.
  • refreshRun — the fetch run: status (syncing, synced, unchanged, failed), the feed httpStatus, the resulting itemCount, and activationSkippedReason when activation was requested but skipped (e.g. the feed was not modified).
  • activation — the execution result when executeActivation was true and activation ran; otherwise null.

Errors

  • 400 VALIDATION_ERROR — the catalog has no stored feed url (“Catalog does not have a stored feed URL…”), or the feed URL fails public-URL validation.
  • 404 NOT_FOUNDadvertiserId or catalogId does not exist or is not visible to the authenticated account.
See Errors for the full error contract.

Sync catalogs

Push catalog feeds and items

Save catalog transform

Define the fan-out rules

Preview activation

Dry-run the fan-out

Execute activation

Materialize the plan into jobs