The BigCommerce Catalog API manages the product side of a store: it adds and updates products individually or in batches, attaches images and videos, and holds the bulk pricing rules and complex rules that drive what a shopper pays. Products carry custom fields and metafields for structured extra data, can be assigned to categories and sales channels, and expose their customer reviews. It is the product source of truth that a storefront and checkout read from.
The BigCommerce Orders API handles the money and settings side of an order: it captures and voids authorized payments, reads an order's transactions, and creates refund quotes and refunds against a paid order. It also manages global and per-channel order settings and stores order metafields of structured data. It is the post-purchase payment and configuration surface for orders already placed in a store.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbigcommerce.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbigcommerce.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.