Blog Settings

Name: Blog Settings API
Brand: Blog Settings
Availability: InStock

✓ Official Vendor SpecMarketingContent 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.

Quickstart

Get started with Blog Settings 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:
"list hubspot blogs and their settings"

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

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

GET STARTED

Start building with Blog Settings API

Explore with Jentic

View OpenAPI Document

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.

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

Why though Jentic?

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

Credential isolation

HubSpot OAuth tokens and Private App keys live in the encrypted Jentic vault (MAXsystem). Agents only ever hold a scoped execution token, so the underlying HubSpot secret stays out of model context.

Intent-based discovery

Agents search Jentic with intents like 'list hubspot blogs' or 'rollback hubspot blog settings' and receive the matching operation plus a ready-to-fill input schema.

Time to first call

Direct integration: 1-2 days to wire OAuth, paginate the settings list, and handle revision restore. Through Jentic: under an hour from search to first successful call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Blog Posts

The blog posts that live inside the blogs configured here

Use Posts after configuring a blog when the agent needs to publish content into it.

Complementary

Blog Authors

Author profiles attached to posts within these blogs

Use Authors when the agent needs to manage who writes inside the configured blog.

Alternative

CMS Pages

Manages site and landing pages instead of blog posts

Choose Pages when the content type is a marketing page rather than a blog entry.

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.