Get a catalog sync
One catalog sync with the status and counts of its last run (itemsSent, itemsSkipped, itemsDeleted, lastError). Poll it after POST /v1/commerce/catalog-syncs/{syncId}/run to follow a run.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.commerce.getCommerceCatalogSync({ path: { syncId: 'sync_abc123', },});console.log(data);{ "catalogSync": { "id": "string", "accountId": "string", "catalogPlatform": "meta", "catalogAccountId": "string", "catalogId": "string", "runStatus": "pending", "lastRunStartedAt": "2019-08-24T14:15:22Z", "lastRunFinishedAt": "2019-08-24T14:15:22Z", "lastError": "string", "itemsSent": 0, "itemsSkipped": 0, "itemsDeleted": 0, "createdAt": "2019-08-24T14:15:22Z" }}Sync a store into a Meta catalog
Keeps a Meta product catalog in sync with the store, for catalog ads (`goal: catalog_sales`) and Shops. The first full run starts right away in the background; `runStatus` and the item counts report its outcome. Every active product variant that is published to the online store and has an image becomes a catalog item, grouped by product (`item_group_id`). After that, product changes on the store update the catalog within minutes, and a daily full run removes items for products or variants the store no longer has. Items are namespaced to the store, so a catalog can take several stores and a run never touches items it did not create. `catalogAccountId` is a connected facebook, instagram or metaads account whose Meta login can manage the catalog (the catalog_management permission); find catalogs with `GET /v1/ads/catalogs`.
Run a catalog sync now
Queues a full run. Poll GET /v1/commerce/catalog-syncs/{syncId} for the outcome.