API
Pull posts through a developer API when you want full control of your stack.
The API lets your own stack read and publish Blogdat.ai posts. Copy the publishing key from Site settings, call the documented endpoints, and keep your frontend fully under your control.
Useful when the hosted blog is not the final destination — headless sites, internal tools, or custom readers. Generation and Template workflows stay in Blogdat.ai; delivery happens wherever you build.
Site API
Keys and endpoints live next to the site
Open the site’s API docs, copy the publishing key, and authenticate requests from your application. No separate developer portal to hunt through.
Site settings · API
curl https://api.blogdat.ai/blogs \
-H "Authorization: Bearer ••••••"
{ "status": "published" }Use the publishing key from your site settings.
Rotate or regenerate keys from site settings when you need to revoke access.
Start with read/publish calls, then wire them into your own CMS or storefront.
Custom delivery
Keep the reader experience in your codebase
Blogdat.ai remains the content engine. Your app decides layout, routing, and product integrations.
Fetch published posts for a headless frontend or mobile client.
Push approved content into another system when your workflow needs a second destination.
What's included
Built into API
REST endpoints
Call documented endpoints from your own application stack.
Publishing key
Authenticate requests with the key from your site settings.
Read and publish
Fetch posts or push approved content into your workflow.
Custom frontend
Keep full control of how readers experience your content.
