Sales Channels

Push your ZingaShop catalog to external marketplaces and shopping surfaces. The
API lets you check connection status and trigger a sync per storefront; you
connect the accounts and choose which products/categories to include in the
console.

Requires data:read to read status and data:write:* to trigger a sync.

Google Merchant

Status

GET /papi/v1/websites/{website_id}/google-merchant

Returns whether credentials are connected, the service-account identity, and
product counts. No secrets are ever returned.

{
  "has_credentials": true,
  "service_account": "[email protected]",
  "product_counts": { "active": 128, "pending": 3 }
}

Trigger a sync

POST /papi/v1/websites/{website_id}/google-merchant/sync

Query param	Default	Meaning
`full`	`false`	Full re-sync of the whole catalog vs. only changes
`background`	`true`	Queue as a background job (recommended) vs. run inline

Queued (default) returns 202:

{ "queued": true, "jobId": "…" }

Inline (background=false) returns the run statistics directly:

{ "queued": false, "stats": { "created": 4, "updated": 12, "deleted": 0 } }

curl -X POST "https://api-v1.zingasuite.com/papi/v1/websites/<id>/google-merchant/sync?full=true" \
  -H "Authorization: Bearer zk_live_xxx"

Meta Commerce

The Meta Commerce (Facebook/Instagram catalog) endpoints mirror Google Merchant
exactly:

GET  /papi/v1/websites/{website_id}/meta-commerce
POST /papi/v1/websites/{website_id}/meta-commerce/sync

Same status shape, same full / background parameters, and the same
{ queued, jobId } or { queued, stats } response.

Notes

Which products and categories are included in a channel is controlled by a
per-item selection in the console — see the ZingaShop
Sales Channels guide.
If an upstream provider rejects the sync, the endpoint surfaces a 502 with
the provider's error text.