Snapps

Connect Snapps to Citeca and publish articles automatically.

Connect Snapps and Citeca publishes finished articles straight into it — live, or as drafts for you to review first.

Setup time

About 2 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#

  • Your Snapps API key (Settings → API Key)
  • The Site ID of the site to publish to (My Sites → ⋮ → Copy Site ID)

About “Not secure” on your free Snapps address

Snapps doesn’t give its free addresses (….verifiedsecure.net) a security certificate, so browsers show them as “Not secure”. That’s on Snapps’ side, not Citeca’s: your articles still publish, and Citeca links to them in a way that opens. For the padlock, connect your own domain: in Snapps, open Edit Site, then More → Settings → Site Domain and click Change site URL. Snapps adds the certificate by itself once your domain is set up.

Connecting Snapps#

Open Settings → Publishing, find Snapps and press Connect. The wizard walks you through the steps below.

  1. 1

    How Snapps works with Citeca

    Two things to copy from Snapps, then it runs by itself.

    • Confirm: I’m signed in to Snapps
    • You’ll copy your API key, which lets Citeca post to your blog.
    • And your Site ID, which tells Citeca which site to post to.
    Open Snapps

    Note

    Citeca publishes through Snapps’ own Blog API, so there’s nothing to install. Your articles appear on your Snapps blog, in your site’s fonts and colours.

  2. 2

    Copy your API key

    In your Snapps account settings.

    • Click API Key in the settings menu.
    • No key yet? Click Generate API Key.
    • Click Copy API Key and paste it below.
    • API key — Use the Copy API Key button so you get the whole key.
    Open Snapps Settings
  3. 3

    Copy your Site ID

    From My Sites in Snapps.

    • Find the site you want your articles on.
    • Click the three dots (⋮) at the top right of its card.
    • Click Copy Site ID and paste it below.
    • Site ID — A short code. It isn’t the number in the address bar or your web address.
    Open My Sites
  4. 4

    Last details

    How your articles appear.

    • Author name (optional) — Shown under each article’s title. Leave blank to use your business name.
    • Publish automatically — Articles go live on your Snapps blog as soon as they’re ready.
    • Save as drafts — Articles wait in Snapps as drafts, so you can review and publish them yourself.

    Note

    Still on your free Snapps address (….verifiedsecure.net)? Browsers show it as “Not secure”, because Snapps doesn’t give that address a security certificate. Your articles still publish and open fine. For the padlock, connect your own domain: in Snapps, open Edit Site, then More, Settings, Site Domain and click Change site URL. Snapps adds the certificate by itself once your domain is set up.

Snapps is connected

Each article now publishes to your Snapps blog by itself, with its cover photo on your blog page. Citeca opens it on your site to check it’s live.

Check it worked#

Verify it’s working

3 checks

  • The Snapps card shows Connected with your site’s address.
  • Your first article is in your site’s blog in Snapps (Edit Site → Blog), with its cover photo.
  • It opens on your site at yoursite/article-name, and in Citeca it shows Live with a link to it.

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 Snapps 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 Snapps 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.

Troubleshooting

Questions#

Snapps says the Site ID doesn’t belong to my account.

Copy it with the button: My Sites → the three dots on your site → Copy Site ID. It’s a short code like ab12cd34. The number in your browser’s address bar and your web address won’t work.

The API key is refused.

In Snapps open Settings → API Key and click Copy API Key rather than selecting the dots. If you clicked Generate API Key again since connecting, the old key stopped working: paste the new one.

Can I edit an article after it’s published?

Yes. Edit it in Citeca and publish again: Citeca replaces the post on your Snapps blog at the same address, keeping its original date. Edits made inside Snapps are overwritten the next time Citeca republishes that article.

Can I review articles before they go live?

Choose Save as drafts when you connect. Articles then wait in your Snapps blog as drafts until you publish them there.

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.

Still stuck?

Can’t find the answer? Ask a person.

Tell us what you were trying to do and where it stopped. If the answer belongs in these docs, we add it here too.

Already a customer? Open your dashboard