WooCommerce
REST API keys, v3 products, variations, and host-specific rate limits.
API keys
In WooCommerce → Settings → Advanced → REST API, create a key with **Read/Write** for products. Paste consumer key and secret in the Destinations WooCommerce modal, plus the store origin (https://shop.example).
Keys are encrypted at rest. Do not use a read-only key if you expect eListSync to create products.
Verification
Before save, eListSync calls /wp-json/wc/v3 (store index or a cheap authenticated route). A 401 means key/secret mismatch or application passwords vs REST keys confusion. A 404 often means permalinks are not set to “Post name” or the REST API is disabled by a security plugin.
What we send
Canonical products become Woo REST products with variations when Size/Color exist. Stock and SKU map onto variation fields. Images are URLs; Woo downloads them if the server allowlists outbound HTTP.
Permalinks and HTTPS
Woo REST almost always needs pretty permalinks. Mixed content (HTTP store, HTTPS images) can fail image sideload. Use HTTPS on the shop.
Common errors
- 401 invalid key — regenerate in Woo, paste again
- 404 rest_no_route — permalinks or security plugin blocking
/wp-json/ - SKU exists — Woo unique SKU; change canonical SKU or update in Woo
- Timeout — cheap hosts rate-limit; bulkhead will retry with backoff