Official vendor OpenAPI document · agent-readyMarketingContent Managementoauth2, apiKey14 EndpointsREST
For Agents
Create, update, and organise HubSpot blog tags in batches and across multi-language variation groups. Useful for agents that publish or curate blog taxonomy.
Use for: Create a new blog tag for a HubSpot blog post, Update the name of an existing blog tag, Archive multiple unused blog tags in one batch call, List all blog tags currently published on the HubSpot CMS
Not supported: Does not handle blog post content, page rendering, or site search indexing - use for HubSpot blog tag taxonomy management only.
The HubSpot Tags API manages blog tags within the HubSpot CMS, including creation, batch updates, archival, and multi-language tag groupings. It supports attaching tags to language variation groups, designating primary languages, and reading tag metadata for use across HubSpot blog content. Tags are scoped to the HubSpot blog system and link blog posts to topical taxonomies for site search and content organisation.
Install Jentic One Beta
Connect the Tags to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tags, 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-tags" | 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-tags" | 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 Tags API.
Create individual or batched blog tags with name and slug values
Update existing blog tag records and rename tags across the CMS
Archive blog tags singly or in batches without affecting tagged posts
Attach blog tags to multi-language variation groups for translated content
Set a new primary language for a tag's translation group
Detach a blog tag from its multi-language group
Retrieve a paginated list of all blog tags or a batch by ID
Use Cases
Patterns agents use Tags API for, with concrete tasks.
★ Bulk Tag Cleanup
Audit and consolidate a HubSpot blog's tag taxonomy by archiving unused tags and merging duplicates. The Tags API supports batch archive and batch update operations so an agent can process dozens of tag records in a single call without rate-limiting on per-record requests. Suitable for content teams cleaning up legacy blogs or merging blog properties.
Read the full list of blog tags via GET /cms/v3/blogs/tags, identify tags with zero associated posts, and call POST /cms/v3/blogs/tags/batch/archive with the unused tag IDs.
Multi-Language Blog Tag Localisation
Maintain translated tag variants across a multilingual HubSpot blog. The API exposes endpoints for attaching, detaching, and creating language variations and for setting the primary language of a tag group. This allows an agent to keep tag translations in sync with localised blog posts and reassign primary languages when the source content changes.
Call POST /cms/v3/blogs/tags/multi-language/create-language-variation to create a French variant of an English tag, then POST /cms/v3/blogs/tags/multi-language/attach-to-lang-group to link it to the source group.
Programmatic Tag Provisioning
Provision a fixed taxonomy of blog tags as part of a HubSpot blog rollout or migration. The batch create endpoint accepts up to 100 tag definitions per call, so a migration script or agent can import a taxonomy from another CMS in seconds rather than creating each tag individually through the UI.
Read a CSV of 50 tag names, build a batch payload, and POST /cms/v3/blogs/tags/batch/create to provision them in one request.
Agent-Driven Editorial Workflow
Use Jentic to give an editorial AI agent the ability to maintain HubSpot blog tags as part of a wider content workflow. The agent searches Jentic for the relevant tag operation, loads the input schema, and executes the call without browsing HubSpot's developer docs. Credential isolation keeps the HubSpot private app token out of the agent's reasoning context.
Use Jentic search query 'create a HubSpot blog tag', load the schema for POST /cms/v3/blogs/tags, and execute the call with the tag name from the editorial brief.
Key Endpoints
14 endpoints — the hubspot tags api manages blog tags within the hubspot cms, including creation, batch updates, archival, and multi-language tag groupings.
METHOD
PATH
DESCRIPTION
GET
/cms/v3/blogs/tags
List all blog tags
POST
/cms/v3/blogs/tags
Create a new blog tag
PATCH
/cms/v3/blogs/tags/{objectId}
Update a blog tag
DELETE
/cms/v3/blogs/tags/{objectId}
Archive a blog tag
POST
/cms/v3/blogs/tags/batch/create
Create a batch of blog tags
POST
/cms/v3/blogs/tags/batch/archive
Archive a batch of blog tags
POST
/cms/v3/blogs/tags/multi-language/create-language-variation
Create a translated tag variant
GET
/cms/v3/blogs/tags
List all blog tags
POST
/cms/v3/blogs/tags
Create a new blog tag
PATCH
/cms/v3/blogs/tags/{objectId}
Update a blog tag
DELETE
/cms/v3/blogs/tags/{objectId}
Archive a blog tag
POST
/cms/v3/blogs/tags/batch/create
Create a batch of blog tags
POST
/cms/v3/blogs/tags/batch/archive
Archive a batch of blog tags
POST
/cms/v3/blogs/tags/multi-language/create-language-variation
Create a translated tag variant
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.
T
Tags
- Foundational (C)56/100
74
Foundational Compliance64
Developer Experience & Jentic Compatibility32
AI-Readiness & Agent Experience94
Agent Usability70
Security71
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
5%
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.
32
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
70%
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.
56%
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).
71
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
71%
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 Tags by hand means registering an OAuth app or minting a private app token, targeting api.hubapi.com, and coding the create, patch, batch, and language-variation calls yourself. Through Jentic you install once, import Tags from the API Directory, store the token once, and your agent calls it.
Permission scoping
Tags puts the tag id in the URL path (/cms/v3/blogs/tags/{objectId}) for individual edits, so a rule can pin your agent to reading or updating one tag. You choose the operations it may call, so deleting a tag 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 tag' or 'list blog tags', and Jentic returns the matching Tags 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 Tags API through Jentic.
What authentication does the HubSpot Tags API use?
The Tags API accepts HubSpot OAuth 2.0 access tokens (legacy authorization code flow) or a private app token sent in the `private-app-legacy` header. Through Jentic, the token is stored encrypted in the vault and never enters the agent's prompt context.
Can I update many blog tags in a single request with the Tags API?
Yes. POST /cms/v3/blogs/tags/batch/update accepts a batch of tag updates in one call, and there are matching batch endpoints for create, read, and archive under /cms/v3/blogs/tags/batch/.
What are the rate limits for the HubSpot Tags API?
HubSpot enforces account-wide CMS API limits - typically 100 requests per 10 seconds for OAuth apps and 250,000 daily on most paid tiers. Use the batch endpoints to reduce request volume on tag-heavy operations.
How do I create a new blog tag through Jentic?
Search Jentic with the query `create a HubSpot blog tag`, load the schema for POST /cms/v3/blogs/tags, and execute with the tag name and slug. Install the SDK with `pip install jentic` and authenticate using your `JENTIC_AGENT_API_KEY`.
Does the Tags API support multilingual blog content?
Yes. The endpoints under /cms/v3/blogs/tags/multi-language/ let you attach tags to language groups, create language variations, set a primary language, and detach tags from a group, so a single tag concept can have synchronised translations.
Can I limit what my agent is allowed to do with the HubSpot Tags API?
Yes. Jentic One is self-hosted by you, so your own rules decide which HubSpot Tags operations and credentials the agent may use. Because the API puts the tag id in the URL path (/cms/v3/blogs/tags/{objectId}), you can pin the agent to reading or updating a single tag, and destructive calls such as DELETE /cms/v3/blogs/tags/{objectId} or POST /cms/v3/blogs/tags/batch/archive are only reachable if you explicitly include them. The stored HubSpot token is injected at execution time and never enters the agent's prompt.
GET STARTED