The blogmate API docs.Your blog, as an endpoint.
This page is the blogmate API docs at a glance: what the publishing API covers, the shape a post comes back in, and how to get the full reference. Enough to decide whether it fits your stack before you write a line.
3 days free · Cancel anytime · GDPR compliant
What the blogmate API covers.
Four concepts carry the whole surface. If your use case fits these, the API covers it.
Posts
List and fetch published articles: title, slug, excerpt, body, and publish date, as JSON your front end renders directly. Nothing to scrape, nothing to parse out of a theme.
Scheduling
Read the queue: what is planned, for when, and what state each post is in. Useful for previews, staging builds, and knowing what tomorrow morning brings.
Workspaces
One token per blog. Agencies and multi-brand teams keep each client's content behind its own credentials, with nothing shared between workspaces.
Webhooks
Get notified the moment a post ships instead of polling for it. Trigger a rebuild, purge a cache, or ping your team chat.
The post object.
The shape you render. Field names below are illustrative - the reference that ships with your keys is exact.
The body arrives as HTML, ready to render.
Get access.
API access is included, like everything else. The full reference - every endpoint, authentication, rate limits, webhook payloads - ships with your keys. If you are weighing a build, ask us first: we will tell you honestly whether the API fits it.
Developer questions.
Honest answers, before you build.
What are the rate limits?
The exact numbers ship with your keys and are documented per endpoint. Blogs are read-heavy and the API is built for that; if your use case needs more headroom, ask.
Are there SDKs?
Not yet. The API is plain JSON over HTTPS with a Bearer token, so a fetch call is the whole client. If you build a wrapper worth sharing, we would genuinely like to see it.
Can I build my own front end?
Yes - that is the point. blogmate handles research, writing, and scheduling; your code decides how posts render. Static build, server-rendered, native app: if it speaks HTTP, it can serve your blog.
Does the API cost extra?
No. One plan, and the API is in it - along with daily publishing. The trial includes API access too, though three days is tight for building an integration; most people wire it up after the first month has started.
Build on it.
Start the trial and watch the posts arrive. When you are ready to render them your own way, the API is already there - no upgrade to buy.