Custom blog API
Connect Custom blog API to Citeca and publish articles automatically.
Connect Custom blog API 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.
Connecting Custom blog API#
Open Settings → Publishing, find Custom blog API and press Connect. The wizard walks you through the steps below.
- 1
Add your blog API
The address and token your developer gave you. Citeca creates and updates posts there, nothing else.
- Your developer’s API must accept these calls (with Authorization: Bearer <token>):
- Each post is sent as JSON with these fields:
- API base URL — The address before /posts. We check it by listing your posts.
- API token — Stored encrypted. Only used to create and update your blog posts.
- 2
Author & publishing
Set a byline and choose how new articles should appear.
- Author name (optional)
- Publish on schedule — Articles go live on your blog on their day.
- Send as drafts — Articles arrive as drafts for your team to review and publish.
Blog API connected
Every new article is sent to your blog API on schedule, with its title, cover, summary and author.
Check it worked#
Verify it’s working
4 checks
- The platform’s card in Settings → Publishing shows a Connected badge.
- Publishing an article from the editor returns a link or a Draft on site badge.
- The article appears in your platform’s own content list.
- Opening it on your live site shows headings, images and links intact.
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 Custom blog API 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 Custom blog API 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#
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.