Blogger API

Name: Blogger API API
Brand: Blogger API
Availability: InStock

✓ Official Vendor SpecMarketingContent Managementoauth233 EndpointsREST

For Agents

Read, publish, and moderate posts, pages, and comments on Google Blogger blogs. Agents can draft posts, schedule publishes, and approve or remove comments.

Quickstart

Get started with Blogger API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"publish a post to a Blogger blog"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Blogger API API.

List, search, and retrieve posts on a blog with filters by status and labels

Create, patch, publish, or revert blog posts including scheduled publishes

Manage pages on a blog, including publishing and reverting page revisions

Read and moderate comments — approve, mark as spam, or remove

GET STARTED

Start building with Blogger API API

Explore with Jentic

View OpenAPI Document

The Blogger API exposes Google Blogger blogs, posts, pages, comments, and pageviews so applications can publish, edit, and moderate content programmatically. It supports listing posts by status (draft, live, scheduled), publishing and reverting drafts, searching posts within a blog, and managing the comment moderation queue. The same API powers external content tools, scheduled cross-posters, and migration utilities. Read access works with API keys for public blogs, while authoring requires OAuth-authenticated calls under the blog owner's account.

Use Cases

Patterns agents use Blogger API API for, with concrete tasks.

★ Programmatic Content Publishing

Drive a content workflow that drafts in an editorial system and publishes to Blogger automatically. Posts are managed at /v3/blogs/{blogId}/posts with publish at /v3/blogs/{blogId}/posts/{postId}/publish and revert at .../revert. Scheduling is supported by setting publish on a future timestamp.

Insert a draft post on blog 1234567890 with the supplied title and HTML content, then publish it immediately.

Cross-Platform Content Sync

Mirror posts from a primary CMS into Blogger as a secondary distribution channel. Use list and search at /v3/blogs/{blogId}/posts/search to detect existing posts and patch them via PATCH /v3/blogs/{blogId}/posts/{postId} when source content updates. The same flow can also revert posts to draft if the source removes them.

Search posts on blog 1234567890 for the source slug, and either patch the existing post or create a new one with the supplied content.

Comment Moderation

List pending comments and act on each — approve, mark as spam, or delete. Comments are managed at /v3/blogs/{blogId}/posts/{postId}/comments with explicit approve, markAsSpam, and removeContent endpoints. Combined with a moderation policy, this allows a hands-off comment pipeline.

List all pending comments on post 555 of blog 1234567890 and approve any whose author email matches the trusted-commenters list.

Reader Analytics

Pull blog-level pageview stats from /v3/blogs/{blogId}/pageviews and feed them into a dashboard or spreadsheet. The endpoint returns counts by time range so editors can see which periods drove traffic without leaving their analytics tool.

Get pageviews for blog 1234567890 for the last 30 days and return totals per day.

Agent-Driven Editorial

An AI agent receives a brief, drafts a post, and publishes it to Blogger via Jentic, then monitors the comment queue. The agent loads the insert post and publish operations, applies the right blogId, and handles credential injection through Jentic. OAuth tokens stay in the vault; the agent only ever sees a scoped access token.

From the brief 'announce v2 launch on the company blog with these talking points', insert a draft, publish it, and then approve any non-spam comments arriving in the next hour.

Key Endpoints

33 endpoints — the blogger api exposes google blogger blogs, posts, pages, comments, and pageviews so applications can publish, edit, and moderate content programmatically.

METHOD

PATH

DESCRIPTION

GET

/v3/blogs/byurl

Look up a blog by public URL

GET

/v3/blogs/{blogId}/posts

List posts on a blog

POST

/v3/blogs/{blogId}/posts

Create a new post on a blog

POST

/v3/blogs/{blogId}/posts/{postId}/publish

Publish a draft or scheduled post

POST

/v3/blogs/{blogId}/posts/{postId}/revert

Revert a post to draft

PATCH

/v3/blogs/{blogId}/pages/{pageId}

Patch a page on a blog

GET

/v3/blogs/{blogId}/pageviews

Get pageview stats for a blog

GET

/v3/blogs/byurl

Look up a blog by public URL

GET

/v3/blogs/{blogId}/posts

List posts on a blog

POST

/v3/blogs/{blogId}/posts

Create a new post on a blog

POST

/v3/blogs/{blogId}/posts/{postId}/publish

Publish a draft or scheduled post

POST

/v3/blogs/{blogId}/posts/{postId}/revert

Revert a post to draft

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive short-lived scoped access tokens at execution time and never hold the refresh token.

Intent-based discovery

Agents search Jentic with intents like 'publish a blog post' or 'moderate a comment' and Jentic returns the matching Blogger operation with its full input schema, so the agent can call the right endpoint without browsing the Discovery doc.

Time to first call

Direct integration: half a day to a day for OAuth, scopes, and the post/comment moderation flow. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Ghost API

Open-source publishing platform with content and admin APIs.

Choose Ghost when the team owns the publishing platform; choose Blogger when content lives on Google's hosted Blogger blogs.

Alternative

Webflow API

Publishing, CMS, and ecommerce APIs for Webflow sites.

Choose Webflow when content goes to a Webflow site; choose Blogger for Blogger-hosted content.

Complementary

Custom Search API

Indexes and searches public content including Blogger sites.

Use Custom Search to power on-blog search across published Blogger content.

FAQs

Specific to using Blogger API API through Jentic.

What authentication does the Blogger API use?

The Blogger API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/blogger scope for read/write and https://www.googleapis.com/auth/blogger.readonly for read-only access. Through Jentic, the OAuth refresh token sits in the encrypted vault and the agent only receives short-lived scoped access tokens.

Can I schedule a post to publish later with this API?

Yes. POST /v3/blogs/{blogId}/posts/{postId}/publish accepts a publishDate query parameter; setting it to a future RFC3339 timestamp schedules the post. Calling /publish again without publishDate publishes immediately.

What are the rate limits for the Blogger API?

Blogger uses Google's standard project-level quotas — typically a few requests per second per user with a daily cap that you can monitor in the Google Cloud quotas console. Bulk publishing should pace inserts to stay well under the per-user QPS.

How do I publish a post through Jentic?

Search Jentic for 'publish a Blogger post', load the schema for POST /v3/blogs/{blogId}/posts followed by POST /v3/blogs/{blogId}/posts/{postId}/publish, and execute. Jentic injects the OAuth token, so the agent only supplies blogId, the post body, and (optionally) the publishDate.

Is the Blogger API free?

Yes — Blogger is a free product and the API has no per-call cost. The only practical limits are the Google Cloud project quotas and the OAuth scopes you have authorised.

Can I moderate comments programmatically?

Yes. List pending comments via /v3/blogs/{blogId}/posts/{postId}/comments?status=pending and act on each with the approve, markAsSpam, or removeContent endpoints under the same path. This lets you build automated policies without using the Blogger UI.