BigCommerce
Connect BigCommerce to Citeca and publish articles automatically.
Connect BigCommerce and Citeca publishes finished articles straight into it — live, or as drafts for you to review first.
Setup time
About 4 minutes
Access needed
Admin on the site or store
What we touch
Blog posts only
Note
This connection can only read and publish blog posts. Your theme, products and settings are never modified.
What you need#
- Access to your BigCommerce store admin
- One API account with Content set to modify (we show you where)
- Optional: your WebDAV username and password, for cover images
Your store doesn’t need to be launched
Articles are added to your store blog straight away. While the store shows “Coming Soon” to visitors, Citeca marks them Store not launched and switches them to Live by itself once you launch.
Connecting BigCommerce#
Open Settings → Publishing, find BigCommerce and press Connect. The wizard walks you through the steps below.
- 1
Before you start
One quick check. The whole setup takes about 4 minutes.
- Confirm: I can sign in to my BigCommerce store admin
- Sign in to your store admin in another tab, then come back here.
- Your store doesn’t need to be launched yet. Articles wait in your blog and appear when you launch.
Note
This connection can only read and publish blog posts. Your theme, products, and settings are never touched. You’ll copy three things from your BigCommerce admin: your store address, one access token, and (for cover images) a WebDAV password.
- 2
Your store address
So the next buttons open your own store.
- Store address — Copy the address from your browser while you’re in your BigCommerce admin. It starts with store- and ends with .mybigcommerce.com.
- 3
Create an API account
This gives Citeca permission to write blog posts, and nothing else.
- Name it
- Under OAuth scopes, find Content and click
- Leave everything else on None, then click Save.
- BigCommerce shows your credentials once. Copy the Access token (the last one).
Heads up
Trial stores can have only one API account. If BigCommerce greys out “Create API account”, delete the old one first (its ••• menu → Delete).
- 4
Paste your access token
We check it with BigCommerce on connect, so a green check means publishing works.
- Access token — The Access token from the credentials box (not the Client ID or Client secret).
- 5
Cover images
Recommended. Lets us put each article’s cover image into your store, so your blog page shows it.
- Copy the WebDAV Username (your account email) and the WebDAV Password from that page.
- Skip this and articles still publish, just without a cover image on your blog page.
- WebDAV username (optional)
- WebDAV password (optional)
- 6
Author & publishing
Last details: a byline, and whether articles go live by themselves.
- Author name (optional) — Shown as the byline. Leave it empty to use your business name.
- Publish immediately — Articles go live on your store blog on their scheduled day.
- Save as draft — Articles arrive unpublished in BigCommerce for you to review and publish.
BigCommerce is connected
We can reach your store blog. New articles publish to it automatically, with their cover image in your store.
Check it worked#
Verify it’s working
3 checks
- The BigCommerce card shows Connected.
- Your first article is in Storefront → Blog in your admin, with its cover image.
- It opens on your store at
/blog/your-article/(from your admin’s “View storefront” while not launched).
To test without waiting for a scheduled article, open any finished article in Blog content and press Publish. You get a result per destination immediately, including the exact error if something is wrong.
Managing the connection#
Once connected, the BigCommerce card shows a green Connected dot and a Manage button. Everything about the connection is changed from there — there are three controls.
- Test connection — checks the credentials against BigCommerce right now. If they fail you get the platform’s own response, not a generic message.
- Reconnect — walks through the setup again. This is how you paste a rotated token, publish somewhere else, or change whether articles go live or wait as drafts. It replaces what is stored rather than adding a second connection.
- Disconnect — deletes the stored credentials and stops publishing. Articles already published stay on your site untouched, and your drafts and schedule in Citeca are kept.
Note
When something fails you get a plain explanation and the steps to fix it. The platform’s own response — status code, endpoint and response body — is folded away under Details for support; “Copy error report” puts all of it in one paste for a support message.
TroubleshootingQuestions#
“Create API account” is greyed out.
Trial stores allow one Store-level API account. Delete the old one first: its ••• menu → Delete → tick the box → Delete. Then create the new one.
The access token is refused.
Paste the Access token (the last of the three values), not the Client ID or Client secret. If it still fails, the account was made without Content → modify: create a new one with that scope.
My articles have no cover image on the blog page.
Add your WebDAV username and password (Settings → File access) to the connection. Without them articles still publish, just without a cover.
Where do I find my store address?
It’s in your browser while you’re in your admin: store-xxxx.mybigcommerce.com. Paste the whole address; we take what we need.
Where do I change whether articles go live or stay as drafts?
Press Manage on the connection’s card in Settings → Publishing, then Reconnect, and answer the live-or-draft step differently. It applies to that connection only, so your other destinations are unaffected.
What happens if I regenerate the credentials?
The old ones stop working immediately and publishing fails with an authentication error. Press Manage on the card, then Reconnect, and paste the new ones — that replaces the old credentials rather than adding a second connection.
Can I disconnect without losing published articles?
Yes. Disconnecting only deletes the credentials we stored. Everything already published stays exactly where it is, because those are posts in your own CMS.
Will publishing the same article twice create a duplicate?
No. Articles are matched on their slug, so republishing updates the existing post rather than adding a second one.
Something missing or wrong here? Tell us and we will fix it.