Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Marketing / Hubspot / Posts
Posts logo

HubSpot Posts

Browse all Hubspot APIs
53
AI ReadinessFoundational (C)53/100
See full scorecard
Official vendor OpenAPI document · agent-readyMarketingContent Managementoauth2, apiKey24 EndpointsREST

For Agents

Create, schedule, translate, and version HubSpot blog posts via batch and multi-language endpoints, so an agent can manage a full blog publishing workflow without the HubSpot UI.

Use for: Create a new HubSpot blog post in the marketing blog, Schedule the product launch post for tomorrow at 09:00, Clone the Q3 best-of post as the starting point for Q4, Restore blog post 12345 to revision 6789

Not supported: Does not manage authors, tags, or blog-level configuration, and does not surface post analytics - use for authoring, scheduling, translating, and versioning HubSpot blog posts only.

The HubSpot CMS Blog Posts API manages every blog post in a HubSpot CMS portal, with single and batch endpoints for create, read, update, archive, schedule, draft, and clone. It includes revision endpoints for restoring or restoring-into-draft, plus a multi-language group so the same post can exist in several locales while sharing one identity. Use it for end-to-end programmatic blog publishing - from drafting to scheduling to archive.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Posts to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Posts, 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-posts" | sh
2

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-posts" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Posts API.

Create or update blog posts individually or in batches of dozens at a time

Schedule a blog post to publish at a specific timestamp

Manage post drafts and push the draft live in one call

Clone a published post as the starting point for a new variant

Restore a post to an earlier revision or restore the revision into draft

Attach a post to a multi-language group so translated variants share an identity

Archive obsolete posts in batch without breaking historical URLs

Use Cases

Patterns agents use Posts API for, with concrete tasks.

★ Editorial Calendar Automation

Editorial teams plan content weeks in advance and want each post to appear at a precise time. The schedule endpoint paired with batch create lets an integration ingest a calendar, create the posts in draft, and schedule each for its slot in one orchestrated run. The result is a deterministic publishing pipeline backed by version history.

Read 10 calendar entries, POST them to /cms/v3/blogs/posts/batch/create as drafts, then call /cms/v3/blogs/posts/schedule for each with the planned publish timestamp.

Multi-Language Translation Workflow

Brands publishing in several languages need the translated post tied to the source post for analytics and routing. The multi-language endpoints attach posts to a language group, set a primary, and update language metadata in one call. The original post remains the canonical reference even as translations are added or replaced.

POST to /cms/v3/blogs/posts/multi-language/attach-to-lang-group with the source postId and the translated postIds, then call set-new-lang-primary if the primary language changed.

Content Reuse Through Cloning

Annual or quarterly recap posts share a structure year over year. The clone endpoint duplicates an existing post as a draft so an editor can swap in fresh data without rebuilding the layout. Combined with the draft endpoints, the new post can be reviewed, scheduled, or pushed live with a single call.

POST to /cms/v3/blogs/posts/clone with the source postId, edit the resulting draft via /cms/v3/blogs/posts/{objectId}/draft, then call the draft push-live endpoint.

Pre-Publish Revision Diff

Before a high-stakes post goes live, an editor wants to confirm exactly what changed since the last published version. The revisions endpoints return the change history and a specific revision payload so the agent can render a diff for human approval before pushing the draft live.

GET /cms/v3/blogs/posts/{objectId}/revisions, fetch the latest two revisions, render a diff for the reviewer, and either push the draft live or POST to the restore-to-draft endpoint.

Agent-Driven Blog Publishing

An AI agent given a brief and brand voice rules can produce a complete post end-to-end. Through Jentic the agent searches for the create-post operation, loads the schema, executes it with the drafted content, then calls the schedule endpoint to publish at the planned time. Credentials never leave your Jentic One instance.

Use Jentic to search 'create hubspot blog post', load the schema, execute it with the drafted body and metadata, then call the schedule operation for the agreed publish time.

Key Endpoints

24 endpoints — the hubspot cms blog posts api manages every blog post in a hubspot cms portal, with single and batch endpoints for create, read, update, archive, schedule, draft, and clone.

METHOD

PATH

DESCRIPTION

GET

/cms/v3/blogs/posts

List blog posts

POST

/cms/v3/blogs/posts/batch/create

Create posts in batch

POST

/cms/v3/blogs/posts/batch/update

Update posts in batch

POST

/cms/v3/blogs/posts/batch/archive

Archive posts in batch

POST

/cms/v3/blogs/posts/schedule

Schedule a post to publish

POST

/cms/v3/blogs/posts/clone

Clone an existing post

POST

/cms/v3/blogs/posts/{objectId}/draft

Update the draft of a post

POST

/cms/v3/blogs/posts/{objectId}/draft/push-live

Push the draft of a post live

GET

/cms/v3/blogs/posts

List blog posts

POST

/cms/v3/blogs/posts/batch/create

Create posts in batch

POST

/cms/v3/blogs/posts/batch/update

Update posts in batch

POST

/cms/v3/blogs/posts/batch/archive

Archive posts in batch

POST

/cms/v3/blogs/posts/schedule

Schedule a post to publish

POST

/cms/v3/blogs/posts/clone

Clone an existing post

POST

/cms/v3/blogs/posts/{objectId}/draft

Update the draft of a post

POST

/cms/v3/blogs/posts/{objectId}/draft/push-live

Push the draft of a post live

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.

P

Posts

- Foundational (C)
53/100
72
Foundational Compliance
63
Developer Experience & Jentic Compatibility
28
AI-Readiness & Agent Experience
94
Agent Usability
70
Security
75
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
89%

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.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4
2%

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.

28

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
59%

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.

55%

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).

75

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HubSpot Posts by hand means registering an OAuth app or minting a private app token, targeting api.hubapi.com, and coding the batch create, scheduling, cloning, and draft push-live calls yourself. Through Jentic you install once, import Posts from the API Directory, store the token once, and your agent calls it.

Permission scoping

Posts drives most writes through batch and action endpoints that take a request body, so scope your agent to the operations it needs, such as listing posts or creating a draft. You choose the operations it may call, so pushing a draft live or batch archiving 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 'create a HubSpot blog post' or 'schedule a blog post', and Jentic returns the matching Posts 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.

Complementary

Blog Authors

→

Provides the author records that appear as bylines on these posts

Use Authors first to fetch or create the byline, then attach the author ID to the new post.

Complementary

Blog Tags

→

Manages tags applied to posts for categorisation and filtering

Use Tags when the agent needs to classify a post; use Posts to author and schedule the post itself.

Complementary

Blog Settings

→

Configures the blog containers in which these posts live

Use Blog Settings when the agent needs to choose or configure the blog before posting.

Alternative

CMS Pages

→

Manages site and landing pages instead of blog post records

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

FAQs

Specific to using Posts API through Jentic.

What authentication does the HubSpot Blog Posts API use?

It accepts HubSpot OAuth 2.0 tokens or Private App tokens in the Authorization header with the content scope. Jentic stores those credentials in its encrypted vault so the agent only ever holds a scoped execution token.

Can I publish a post to a specific blog within a multi-blog portal?

Yes. The contentGroupId field in the post payload identifies the destination blog. Combine with the Blog Settings API to list available blogs before choosing the target.

What are the rate limits for the HubSpot Blog Posts API?

It uses 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. Batch endpoints count as one request even when updating many posts.

How do I publish a post on a schedule through Jentic?

Run pip install jentic, search 'schedule hubspot blog post', load the schema, and execute it with the postId and target timestamp. Jentic posts to /cms/v3/blogs/posts/schedule with valid auth headers.

Does the API expose post-level analytics like views and conversions?

No. Engagement and traffic metrics live in HubSpot's analytics endpoints. The Blog Posts API only manages the post object - its content, schedule, and revision state.

Can I clone a post into a different blog?

The clone endpoint /cms/v3/blogs/posts/clone duplicates a post within the same content space. To move it to a different blog, update the contentGroupId on the cloned post via the standard update endpoint before publishing.

Can I limit what my agent is allowed to do with the HubSpot Blog Posts API?

Yes. Jentic One runs self-hosted in your own instance, and you decide which of the API's operations your agent may call, so you can grant read-only access such as listing posts or fetching a draft while withholding write actions. Because most changes flow through batch and action endpoints like batch create, schedule, clone, and draft push-live, higher-impact operations such as pushing a draft live or batch archiving posts are available only if you explicitly include them. The HubSpot OAuth or private app token stays encrypted in your instance and is injected at execution time, so the agent never holds the raw credential or a scope you did not grant.

GET STARTED

Start building with Posts API

Explore with Jentic One
View OpenAPI Document