# Google Blogger

**Canonical:** https://apis.io/providers/google-blogger/  
**APIs profiled:** 2

The Google Blogger API v3 allows you to integrate Blogger content with your application. You can create, read, update, and delete blogs, posts, pages, comments, and user information using RESTful operations with OAuth 2.0 authentication.

## Kin Score — 35.2 / 100 (thin)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.0 from 35.2).

| Facet | Score |
|---|---|
| Discoverability | 68.5 |
| Contract Quality | 64.7 |
| Governance | 9.8 |
| Contract Governance | 9.8 |
| Operational Transparency | 7.9 |
| Developer Ergonomics | 23.8 |
| Commercial Clarity | 26.3 |
| Access Clarity | 26.3 |

## Agent readiness — 29.1 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Freemium · Self-serve signup — onboarding: self-serve, pricing: freemium, trial: no (confidence: high).

## APIs (2)

- **Google Blogger Blogs API** — The Blogs API from Google Blogger — 8 operation(s) for blogs.
- **Google Blogger Users API** — The Users API from Google Blogger — 2 operation(s) for users.

## Agentic access (1)

- **Google Blogger Agentic Access** — 16 operations · 6 acting

## Security (3)

- **Google Blogger Authentication** — apiKey/oauth2 · 2 schemes
- **Google Blogger Domain Security** — TLSv1.3 · HSTS · DMARC
- **Google Blogger Vulnerability Disclosure** — security.txt · contact published

## Plans (1)

- **Google Blogger Plans Pricing**

## Tags

Blogging, CMS, Comments, Google, Pages, Posts, Publishing

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/google-blogger/). Scores are computed from the provider's own public artifacts under a published rubric.