Publishing integration
Publish to your own API
For a stack that is none of the above.
Plenty of sites are not on a CMS at all — a Next.js app with content in a repo, an internal platform, something built in-house years ago. For those, Xeostack posts approved articles to an endpoint you expose and authenticates with a key you issue.
That makes the contract yours: you decide what the endpoint does with an article, where it ends up, and when it goes live.
What you need
- An endpoint that accepts a POST
- An auth key Xeostack should send with it
Setting it up
- Expose an endpoint that accepts the article payload and returns success.
- Issue a key for Xeostack to authenticate with.
- Add both under Website Connection → Custom REST API.
What it does not do
This is the least hands-off option by design. Xeostack can tell you it sent the article and that your endpoint accepted it; whether it rendered correctly on your site is something only your code knows.