All guides
Putting the blog on your site
Give a website or an app a channel key to read posts as JSON, HTML or RSS — and write, import and publish them programmatically.
Marketingabout 6 min
By the end you'll be able to
- Create a channel for each site or app that reads the blog
- Choose whether it gets JSON, HTML or RSS
- Make the HTML come out with your own CSS class names
- Hand a developer an OpenAPI document they can build against
- Load an existing blog in, and let scripts and agents write to it
Walk through it
0 of 8 steps done0%
One channel per consumer — the website, the app, a partner feed. It gets its own key, and you can give each one a different slice of the blog and a different look.
Good to know
- Only published posts whose publication time has arrived are ever visible through a channel. Drafts, scheduled posts and archived ones are not reachable with any key.
- Restricting a channel to some categories is how one blog feeds "Company news" to an app and everything to the website, without duplicating a post.
- Leave the allowed origins blank and any site may read the feed in a browser. Fill them in and only those sites can — worth doing if you would rather nobody else embedded your posts.
- Responses carry an ETag and a short cache window, so a site polling for new posts gets an empty 304 answer until something actually changes.
- Rotating a key takes effect immediately and breaks whatever was using the old one until it is reconfigured.
- The writing half of the API uses a normal Zenia token and an x-brand-id header, not a channel key. A channel key can only ever read published posts — it cannot write anything.
- Listing posts for authoring leaves archived ones out, the same as the screen does. Ask for status=Archived, or add includeArchived=true, to see them.
- An import does not go through review by default: those posts were already published on a real site. Turn that off with the requiresApproval option if you would rather read them again on the way in.
- The same rules apply however a post is written. A post an AI agent writes still needs a person’s sign-off, and still cannot be published until it has one.
Common questions