HubSpot Posts
Browse all Hubspot APIs✓ Official Vendor SpecMarketingContent 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.
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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 the Jentic vault.
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
HubSpot OAuth tokens and Private App keys are stored encrypted in the Jentic vault (MAXsystem). The agent only ever holds a scoped execution token, so the raw HubSpot secret never enters the agent's context.
Intent-based discovery
Agents search Jentic with intents like 'create hubspot blog post' or 'schedule hubspot blog post' and receive the matching operation plus a ready-to-execute input schema.
Time to first call
Direct integration: 2-3 days to wire OAuth, batch creates, scheduling, drafts, and language groups. Through Jentic: under a day to search, load, and execute each operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED