Saltar al contenido principal

Connect your BigCommerce store to Clione

This guide walks you through creating the API token Clione needs to read your catalog, enrich your SEO/AEO/GEO signals, and write the optimized metadata back to your store.

Time required: ~5 minutes. Required access: BigCommerce store admin (account owner, or any user with "Manage API Accounts" permission).

Clione never sees customer data, orders, payment info, or any PII. The scopes below grant access only to your product catalog, content pages, and store settings.

Step 1 — Open the API Accounts panel​

  1. Log in to your BigCommerce store admin: https://store-<your-hash>.mybigcommerce.com
  2. From the left sidebar, go to Settings.
  3. Under the API section, click API Accounts.
  4. Click Create API Account (top right) and choose V2/V3 API token.

Step 2 — Name the account​

FieldValue
NameClione AI
OAuth scopes(see Step 3 below)

Leave everything else at defaults. The name is just for your audit trail — pick anything that helps you recognize it later.

Step 3 — Set the scopes​

Clione needs exactly three scopes. Set them as below. Anything else stays at "None".

ScopeLevelWhy Clione needs it
ProductsModifyRead your products, categories, and brands to enrich them. Write the new meta title, meta description, meta keywords, canonical URL, and structured data back.
ContentModifyRead and update your content pages (About, FAQ, etc). Install and remove the Schema Injector script (the small piece that publishes JSON-LD to your storefront).
Information & SettingsRead-onlyRead store name, currency, time zone — needed for currency-aware structured data. Clione never writes here.

Do NOT enable any of the following — Clione never touches them and granting them would expose data we don't need:

  • Customers, Customer logins
  • Orders, Order Transactions
  • Carts, Checkout content, Shipping
  • Themes, Sites & Routes, Channel Settings, Storefront API Tokens
  • Payments
  • Marketing, Promotions (will be added in a future module with its own scope)

Step 4 — Save and download credentials​

  1. Click Save at the top right.
  2. BigCommerce shows a one-time dialog with your credentials and gives you a .txt file to download.
  3. Download the .txt and keep it safe. BigCommerce will never show these credentials again. If you lose them, you have to create a new account from scratch.

The file contains four values:

Client ID:       <something like p9z4x...>
Client Secret:   <long random string>
Access Token:    <long random string — this is the one Clione needs>
API Path:        https://api.bigcommerce.com/stores/<YOUR_STORE_HASH>/v3/

Step 5 — Send to your Clione contact​

Send your Clione contact:

  1. The whole .txt file, OR
  2. The Access Token + API Path (the other two values are not needed to enable Clione).

Use a secure channel — email is fine if your account is locked down with 2FA; for higher sensitivity use a password manager share link (1Password, Bitwarden, etc.) with a 7-day expiry.

That's all you need to do on your side. Once Clione receives the token, the store appears in your dashboard within minutes and the first catalog sync begins.

Sanity check (optional)​

If you want to verify the token works before sending, run this in any terminal (replace the two placeholders with your real values):

curl -s -H "X-Auth-Token: <ACCESS_TOKEN>" \
  "https://api.bigcommerce.com/stores/<STORE_HASH>/v3/catalog/products?limit=1"

You should see a JSON response with one of your products. If you see an error code, see Troubleshooting below.

Troubleshooting​

401 Unauthorized — The Access Token was copied wrong. Re-open the .txt file and copy the value next to "Access Token" exactly, no leading/trailing spaces.

403 Forbidden when Clione tries to read products — The Products scope is set to "None" instead of "Modify" (or "Read-only" at minimum). Go back to Settings → API Accounts → edit the Clione account → change the scope → Save.

403 Forbidden only when Clione tries to write metadata — The Products scope is at "Read-only" instead of "Modify". Update it to "Modify" and save.

404 Not Found — The Store Hash in the API Path doesn't match your actual store. Double-check the STORE_HASH matches what's in the API Path field of the .txt.

Schema Injector says "Cannot install" — The Content scope is at "Read-only" or "None" instead of "Modify". The Schema Injector needs to create a managed script tag on your storefront.

Currency in JSON-LD is wrong — The Information & Settings scope is missing. Without it, Clione defaults to the platform's reported currency and may fall back to USD. Set it to "Read-only" and save — no other action needed.

Revoking access​

If you ever need to revoke Clione's access:

  1. Settings → API Accounts.
  2. Find the "Clione AI" account.
  3. Click the three-dot menu → Delete.

Within seconds, every Clione request to your store starts returning 401 and your store stops appearing in the Clione dashboard. No data is deleted on either side — you can re-issue a new token at any time to resume.

What happens after Clione has the token​

  1. First sync (1–10 minutes depending on catalog size): Clione pulls your products, categories, and pages. You can watch progress in your Clione dashboard under Sync.
  2. First enrichment (depends on your plan quota): Clione generates the optimized SEO/AEO/GEO signals for the entities you select. You review them before they go live.
  3. Propagation: Once you approve, Clione writes the meta title, meta description, meta keywords, canonical URL, and JSON-LD back to your storefront via the same API token.

Everything is logged. Every write is auditable from the Clione dashboard under Signal Propagation with a full history of before/after values per entity.