Publishes to Custom API
Publish straight into your own content API.
Point MotiBlog at your API’s create endpoint and shape the request body to match your schema. Updates find their way back to the same record.
One project and three articles free. No card required.
What you connect
authorise once, publish from then onYour endpoint URL
POST or PUT
Any headers, including auth
An optional body template mapping article fields to your schema
What publishing to Custom API does
Your schema, not ours
A body template maps the article’s fields into the JSON shape your API expects, so nothing on your side has to change to accept it.
Updates address the record
The id your API returns on create is stored; republishing appends it to the endpoint path and updates that record rather than inserting a new one.
True of every integration
A full article, not a paste job
Each publish carries the title, slug, body, meta description, tags and the generated banner image. Nothing is reformatted by hand afterwards.
Republishing updates in place
The post’s id in your platform is stored on first publish. Publishing the article again updates that post instead of creating a duplicate.
Test before anything ships
Every connection has a test call that verifies the credentials against the platform before an article is ever sent. Your agent can run it too: test_integration.
A log per publish
Every attempt is recorded with its outcome. Failures can be retried without regenerating anything — retry_publish picks up the same article.
The shape of it
One project and three articles free. No card required.