How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Google Blogger

Google Blogger Blogs API

The Blogs API from Google Blogger — 8 operation(s) for blogs.

Documentation Provider Profile APIs.io OpenAPI GitHub

Google Blogger Blogs API is one of 2 APIs that Google Blogger publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Blog. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 14 operations across 8 paths, and defines 7 schemas. It is described by OpenAPI 3.1.0, at version v3.

Requests are made against a single base URL, https://www.googleapis.com/blogger/v3.

14 operations 8 paths 7 schemas 2 DELETE8 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v3
Base URL
https://www.googleapis.com/blogger/v3
Authentication
OAuth 2.0, API Key
Contact
Google
Resource Areas
1

Authentication & Security 2

Google Blogger Blogs API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes. An API key is passed in the query as key (apiKey). By default, every request must be authenticated.

Paths & Operations 14

Across 8 paths, the API surfaces 14 operations — 2 DELETE, 8 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Blogs 14
GET
/blogs/{blogId}
Get a blog
getBlog 1 param → 200
GET
/blogs/byurl
Get a blog by URL
getBlogByUrl 1 param → 200
GET
/blogs/{blogId}/posts
List posts
listPosts 8 params → 200
POST
/blogs/{blogId}/posts
Create a post
insertPost 2 params body → 200
GET
/blogs/{blogId}/posts/{postId}
Get a post
getPost 2 params → 200
PUT
/blogs/{blogId}/posts/{postId}
Update a post
updatePost 2 params body → 200
PATCH
/blogs/{blogId}/posts/{postId}
Patch a post
patchPost 2 params body → 200
DELETE
/blogs/{blogId}/posts/{postId}
Delete a post
deletePost 2 params → 204
GET
/blogs/{blogId}/posts/search
Search posts
searchPosts 2 params → 200
GET
/blogs/{blogId}/pages
List pages
listPages 1 param → 200
POST
/blogs/{blogId}/pages
Create a page
insertPage 1 param body → 200
GET
/blogs/{blogId}/posts/{postId}/comments
List comments
listComments 4 params → 200
GET
/blogs/{blogId}/posts/{postId}/comments/{commentId}
Get a comment
getComment 3 params → 200
DELETE
/blogs/{blogId}/posts/{postId}/comments/{commentId}
Delete a comment
deleteComment 3 params → 204

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Post (13 properties), Page (11 properties), Blog (11 properties), Comment (10 properties). Each schema is shown below with its type and property counts.

PostListResponse
object
3 properties
Post
object
13 properties
PageListResponse
object
2 properties
Blog
object
11 properties
CommentListResponse
object
3 properties
Page
object
11 properties
Comment
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

google-blogger-blogs-api-openapi.yml Raw ↑

Other APIs Google Blogger publishes across the network.

Google Blogger Users API
AE Profile APIs.io
#Blog
← Back to G APIs
API Details
ID
google-blogger:google-blogger-blogs-api
Base URL
https://www.googleapis.com/blogger/v3
Docs
https://developers.google.com/blogger
Provider
Google Blogger
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=google-blogger-blogs-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/google-blogger-blogs-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Google Blogger Blogs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.