HubSpot Blog Settings
Browse all Hubspot APIs54
AI ReadinessFoundational (C)54/100
Official vendor OpenAPI document · agent-readyMarketingContent Managementoauth2, apiKey9 EndpointsREST
For Agents
Read and update HubSpot Blog Settings, including multi-language groupings and revision history, so an agent can keep blog configuration consistent across brands or locales.
Use for: List every blog in the HubSpot portal, Retrieve the settings for blog ID 12345, Get the revision history for the marketing blog, Restore the German blog to last week's settings
Not supported: Does not create new blogs, publish blog posts, or manage authors - use for reading and updating existing HubSpot Blog configuration only.
The HubSpot Blog Settings API manages the configuration of each Blog object in a HubSpot portal - the container that holds posts, authors, tags, and templates. It exposes endpoints for reading and updating per-blog settings, listing revision history, and grouping settings across translated blog variants. Use it when the same configuration change must be applied uniformly across multiple blogs or language editions.
Install Jentic One Beta
Connect the Blog Settings to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blog Settings, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-cms-blog-settings" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhubspot.com%2Fhubspot-cms-blog-settings" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Blog Settings API.
Retrieve current settings for a specific blog by blogId
List every blog configured in the HubSpot portal in one call
Roll a blog's settings back to a prior revision when a change introduces an error
Inspect the full revision history for a blog before approving a configuration change
Attach a blog to a multi-language group so translated blogs share configuration intent
Update settings across every language variant of a blog in one batch call
Use Cases
Patterns agents use Blog Settings API for, with concrete tasks.
★ Multi-Locale Blog Configuration
Brands running translated blogs need shared configuration - categories, root URL, posting cadence - to stay aligned. The multi-language endpoints attach blog variants to one group and propagate updates across them in a single call. The result is fewer drift bugs between locales and a faster path from a configuration change to live blog content.
Group three blogs under one language group via /cms/v3/blog-settings/settings/multi-language/attach-to-lang-group, then call /cms/v3/blog-settings/settings/multi-language/update-languages to apply a shared change.
Configuration Change Approval
When marketing operations changes a blog's URL structure or template, mistakes can break canonical URLs and SEO. The settings revision endpoints let an agent diff the current state against a prior revision, flag the change, and roll back via the revision-restore route if the change is rejected.
Fetch /cms/v3/blog-settings/settings/{blogId}/revisions, compare the latest two revisions, and if the diff is unacceptable POST to the matching revision endpoint to restore the prior version.
Portal Blog Inventory
Agencies managing multiple HubSpot portals need a clean inventory of every blog and its settings. A single GET on the settings root returns every blog object with its configuration, suitable for piping into a governance dashboard or a content audit tool.
Call GET /cms/v3/blog-settings/settings, write each blog's id, language, and rootUrl to a CSV, and flag any blogs whose root URL does not match the brand's domain pattern.
Agent-Driven Blog Setup
An AI agent provisioning a new HubSpot blog needs to set the language, URL, and publish defaults without operator hand-holding. Through Jentic, the agent searches for the settings update operation, loads the schema, and executes the call against the target blog, then verifies via the revision endpoint that the change took effect.
Use Jentic to search 'update hubspot blog settings', load the schema, execute it with the new rootUrl and language, then read /cms/v3/blog-settings/settings/{blogId}/revisions to confirm the new revision.
Key Endpoints
9 endpoints — the hubspot blog settings api manages the configuration of each blog object in a hubspot portal - the container that holds posts, authors, tags, and templates.
METHOD
PATH
DESCRIPTION
GET
/cms/v3/blog-settings/settings
List every blog's settings
GET
/cms/v3/blog-settings/settings/{blogId}
Retrieve settings for one blog
GET
/cms/v3/blog-settings/settings/{blogId}/revisions
List revision history
GET
/cms/v3/blog-settings/settings/{blogId}/revisions/{revisionId}
Read a specific revision
POST
/cms/v3/blog-settings/settings/multi-language/attach-to-lang-group
Attach a blog to a language group
POST
/cms/v3/blog-settings/settings/multi-language/update-languages
Update settings across every language variant
POST
/cms/v3/blog-settings/settings/multi-language/set-new-lang-primary
Set the primary language for a group
GET
/cms/v3/blog-settings/settings
List every blog's settings
GET
/cms/v3/blog-settings/settings/{blogId}
Retrieve settings for one blog
GET
/cms/v3/blog-settings/settings/{blogId}/revisions
List revision history
GET
/cms/v3/blog-settings/settings/{blogId}/revisions/{revisionId}
Read a specific revision
POST
/cms/v3/blog-settings/settings/multi-language/attach-to-lang-group
Attach a blog to a language group
POST
/cms/v3/blog-settings/settings/multi-language/update-languages
Update settings across every language variant
POST
/cms/v3/blog-settings/settings/multi-language/set-new-lang-primary
Set the primary language for a group
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
Blog Settings
- Foundational (C)54/100
74
Foundational Compliance64
Developer Experience & Jentic Compatibility29
AI-Readiness & Agent Experience94
Agent Usability70
Security68
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
94%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
29
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
66%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
70
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
70%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
68
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
68%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring HubSpot Blog Settings by hand means registering an OAuth app or minting a private app token, targeting api.hubapi.com, and coding the revision reads and multi-language calls yourself. Through Jentic you install once, import Blog Settings from the API Directory, store the token once, and your agent calls it.
Permission scoping
Blog Settings puts the blog id in the URL path (/cms/v3/blog-settings/settings/{blogId}), so a rule can pin your agent to one blog: it can read that blog's settings and revisions. You choose the operations it may call, so updating languages or setting a new primary language is only available if you include it.
Credential isolation
Your HubSpot OAuth token or private app token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list HubSpot blogs' or 'read blog settings revisions', and Jentic returns the matching Blog Settings operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Blog Settings API through Jentic.
What authentication does the HubSpot Blog Settings API use?
It accepts HubSpot OAuth 2.0 tokens or Private App tokens in the Authorization header with the content scope. Jentic isolates those credentials in its vault and hands the agent a scoped execution token instead of the raw secret.
Can I create a new blog with the Blog Settings API?
No. The endpoints in this API only read or update existing blog settings - there is no POST to create a brand-new Blog object. New blogs must be created from the HubSpot UI, after which the API can manage their configuration.
What are the rate limits for the HubSpot Blog Settings API?
It shares HubSpot's standard public API caps: 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for Private Apps on Pro and Enterprise. Settings endpoints are infrequently called so rate limits rarely bind.
How do I roll a blog back to an earlier configuration through Jentic?
After pip install jentic, search 'restore hubspot blog settings revision', load the schema, and execute it with the blogId and revisionId. Jentic handles auth and posts to the matching revision endpoint.
Does updating one language variant update the others?
Only when called via /cms/v3/blog-settings/settings/multi-language/update-languages, which propagates the change across the language group. A direct PATCH on a single blogId only modifies that one blog.
Can I limit what my agent is allowed to do with the HubSpot Blog Settings API?
Yes. Because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. Since the blog id sits in the URL path (/cms/v3/blog-settings/settings/{blogId}), you can pin the agent to a single blog and let it only read that blog's settings and revision history. Write operations such as updating language variants or setting a new primary language are available only if you explicitly include them, so the agent cannot change configuration you have not granted.
GET STARTED