Domains

Name: Domains API
Brand: Domains
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey, oauth22 EndpointsREST

For Agents

List connected HubSpot CMS domains and inspect any single domain's SSL status, content types, and primary mapping.

Connect the Domains to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Domains, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 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 Domains API.

List every domain currently connected to a HubSpot CMS portal via GET /cms/v3/domains/

Retrieve a specific domain's full configuration through GET /cms/v3/domains/{domainId}

Inspect each domain's SSL provisioning state for compliance and pre-launch checks

See which content types (website, blog, landing pages, knowledge base) each domain serves

GET STARTED

Start building with Domains API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Domains, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for HubSpot CMS Domains, keeping it validated and agent-ready. The HubSpot CMS Domains API exposes the connected domains attached to a HubSpot CMS portal — including primary, secondary, and HubSpot-hosted preview domains. It returns metadata such as the domain name, whether SSL is provisioned, and which content type (site, blog, landing pages) the domain is mapped to. It is the read surface for understanding which sites a HubSpot portal currently publishes to.

Use Cases

Patterns agents use Domains API for, with concrete tasks.

★ Pre-Launch Domain Audit

Before launching a marketing site, list all connected domains in HubSpot to confirm the new domain is attached, SSL is provisioned, and the right content types are mapped. GET /cms/v3/domains/ returns the full inventory in a single call so a release engineer or agent can verify state before flipping DNS.

GET /cms/v3/domains/ and verify the new domain is present with primary=false and ssl provisioned before cutover.

Compliance and Brand Inventory

For compliance or brand audits, pull every domain across HubSpot portals to confirm only approved domains are active and serving content. The API is read-only, so the audit cannot accidentally change configuration.

GET /cms/v3/domains/ across all connected portals and flag any domain not on the approved-brand list.

Canonical URL Discovery for Sitemaps

When generating sitemaps or canonical URL maps for SEO tooling, identify the HubSpot primary domain by reading /cms/v3/domains/. Mapping the primary domain ensures every URL emitted is the canonical one HubSpot serves.

GET /cms/v3/domains/ and pick the entry where primary is true to use as the canonical base URL for sitemap entries.

AI Agent Domain Inspection via Jentic

An AI agent that runs site-readiness or compliance checks calls Jentic to fetch a HubSpot portal's connected domains and reason about their SSL and content-type configuration without needing direct HubSpot dashboard access.

Search Jentic for list hubspot connected domains, load /cms/v3/domains/, and execute, then summarise SSL and primary status per domain.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for hubspot cms domains, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/cms/v3/domains/

List all connected CMS domains

GET

/cms/v3/domains/{domainId}

Get a single CMS domain

GET

/cms/v3/domains/

List all connected CMS domains

GET

/cms/v3/domains/{domainId}

Get a single CMS domain

Why though Jentic?

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

Credential isolation

HubSpot hapikeys, OAuth tokens, and private-app tokens are stored encrypted in the Jentic vault and injected per call. Agents never see the raw token.

Intent-based discovery

Agents search Jentic with intents like list hubspot connected domains and Jentic returns the matching read endpoints with their input schemas.

Time to first call

Direct integration: 1-2 hours including OAuth scope wiring. Through Jentic: under 15 minutes for the read calls themselves once credentials are stored.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot CMS API

Manage CMS pages, blog posts, and content the domains serve

Pair with the CMS API when the agent needs to read or write the content published on those domains, not just the domain inventory.

Complementary

HubSpot Marketing API

Marketing assets like landing pages and emails that often map to the same HubSpot domains

Use Marketing API for asset-level changes; use Domains for the domain-level mapping context.

Complementary

HubSpot Webhooks API

Subscribe to broader HubSpot CMS and CRM events to trigger domain checks reactively

Use Webhooks to trigger an automated domain audit when a relevant CMS change event fires.

FAQs

Specific to using Domains API through Jentic.

Why is there no official OpenAPI spec for HubSpot Domains?

HubSpot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Domains via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the HubSpot Domains API use?

The Domains API supports HubSpot hapikey (query), OAuth 2.0 authorization code with cms.domains.read or cms.domains.write scopes, and private-app tokens (private-app or private-app-legacy header). Through Jentic, the configured credential is held in the encrypted vault and injected at execution.

Can I create or modify a domain through this API?

No. The CMS Domains API exposes read-only operations: GET /cms/v3/domains/ to list and GET /cms/v3/domains/{domainId} to retrieve a single domain. Connecting or removing domains is done through the HubSpot dashboard.

What are the rate limits for the HubSpot Domains API?

Rate limits follow HubSpot's standard tiers — typically 100 requests per 10 seconds per hapikey, higher under OAuth on Enterprise plans. Domain inventories rarely require high call volume, so limits are unlikely to be hit in normal use.

How do I check SSL status for a specific HubSpot domain through Jentic?

Search Jentic for get a hubspot domain, load GET /cms/v3/domains/{domainId}, and execute with the domainId. The response includes the SSL provisioning state alongside content-type mapping.

Does the API distinguish between primary and secondary domains?

Yes. Each domain entry returned from /cms/v3/domains/ includes a primary boolean indicating whether HubSpot treats it as the canonical domain for the portal.