A headless marketing site
Generate and schedule in Blogdat. Render the posts in the frontend you already ship.
SEO blog API for headless sites and custom frontends
Site settings · API
Developer API
curl https://api.blogdat.ai/blogs \
-H "Authorization: Bearer ••••••"
{ "status": "published" }Use the publishing key from your site settings.
Rotate the key on the same screen when a contractor leaves or a credential leaks. The old key should stop without a support ticket.
Blogdat.ai remains the place that researches, drafts, attaches the image, and runs the schedule. Your app decides the layout, the routing, and whatever else wraps the article. That is the right split for a headless site, a storefront, or an internal tool that already has a frontend you do not want to replace. The hosted blog is optional once you are delivering the HTML yourself. You can still use the hosted blog on another site in the same workspace. The API does not force every site onto the same delivery path.
How it works
The SEO blog API lets your stack read and publish the articles Blogdat.ai writes. You copy the publishing key from the site settings and call the documented endpoints. A headless frontend, a custom CMS, or an internal tool can list posts, fetch a body, and trigger publish while the research, template, and schedule stay in Blogdat.
The article your frontend renders should be the article that was indexed: same title, same slug, same cover, same language. The API is how a custom site keeps that contract. Authentication uses the site key, so each site stays isolated inside a workspace that may hold many clients.
Use the API when WordPress is not the destination and the hosted blog theme is not the one you want readers to see. You still get keyword research, drafts, translations, and indexing on the URL your frontend serves.
Use cases
An internal publishing tool
Pull drafts into the review system your company built, then publish back through the API.
One content engine, several frontends
Different sites call their own keys. Templates and languages stay configured per site.
What is included
- REST endpoints
- Call documented endpoints from your own backend or frontend.
- Publishing key
- Authenticate with the key stored on the site, and rotate it there.
- Read and publish
- Read posts out, or push approved content into your workflow.
- Custom frontend
- Keep full control of how readers see the article.
How it connects
The API delivers the output of the writer, research, images, and languages. Your own domain and indexing should point at the URL the frontend canonicalizes. Audience insights can sit on that same public host.
Search topics
- seo blog api
- blogging api
- headless blog api
- content automation api
