CMS Content Audit

Name: CMS Content Audit API
Brand: CMS Content Audit
Availability: InStock

✓ Official Vendor SpecMarketingContent Managementoauth2, apiKey1 EndpointsREST

For Agents

Query HubSpot CMS audit logs to see who changed which page, post, or template, and when, so an agent can answer compliance questions or detect unexpected edits.

Quickstart

Get started with CMS Content Audit 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:
"query hubspot cms audit logs"

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

Capabilities

What an agent can do with CMS Content Audit API.

Query CMS audit log events by date range, user, and content object

Detect unauthorised edits to landing pages or site pages by filtering for unfamiliar user IDs

Reconstruct the edit history of a specific CMS object before publishing a rollback

Feed CMS change events into a SIEM or compliance dashboard via scheduled pulls

GET STARTED

Start building with CMS Content Audit API

Explore with Jentic

View OpenAPI Document

Use for: List all CMS edits made yesterday, Find every change made to landing page 12345 in the last 30 days, Check whether user 999 modified any CMS content this week, Retrieve the audit trail for the homepage before approving a rollback

Not supported: Does not modify CMS content or surface non-CMS portal events — use for querying read-only HubSpot CMS audit logs only.

The HubSpot CMS Content Audit API exposes a single read endpoint for querying audit logs of CMS changes that occurred on a HubSpot account. It returns who changed what content, when, and from which interface, making it the system of record for compliance reviews and post-incident investigation of CMS edits. The endpoint supports filters for date range, user, and content type so an agent can fetch only the events relevant to a given audit window.

Use Cases

Patterns agents use CMS Content Audit API for, with concrete tasks.

★ Compliance Audit Trail

Regulated industries require a tamper-evident record of who changed customer-facing content and when. The CMS Content Audit endpoint returns those events with user, timestamp, and content references in JSON, ready to feed into a compliance archive. Pulling the log nightly and storing it externally provides defensible evidence of governance over public content.

Call GET /cms/v3/audit-logs/ with a 24-hour window, write each event to long-term storage, and surface any event whose userId is not on an approved-editor list.

Pre-Rollback Investigation

Before reverting a CMS object, an editor needs to know what changed and who made the change. The audit endpoint returns the chronological event list for the object, supporting a confident rollback decision. Combining it with the Pages or Posts revision endpoints completes the picture of which revision to restore.

Query /cms/v3/audit-logs/ for objectId 12345 over the last 14 days, present the user, timestamp, and event type for each entry, and recommend the latest known-good revision to restore.

Out-of-Hours Change Monitor

Marketing teams sometimes set policies that production CMS edits should not happen outside working hours. A scheduled agent pulls the audit log every hour, filters events with timestamps outside business windows, and posts an alert into Slack. The single-endpoint design makes the integration trivially small.

Hourly, GET /cms/v3/audit-logs/ for the previous hour, filter events with timestamp outside 09:00-18:00 local time, and post each to a Slack webhook.

Agent-Driven Audit Lookup

An AI compliance agent answering an auditor's question must produce evidence quickly. Through Jentic, the agent searches for the CMS audit operation, loads the schema, and executes it with the requested filters. The structured response is returned to the agent for summarisation, with credentials handled by Jentic rather than the agent.

Use Jentic to search 'hubspot cms audit log query', load the schema, execute it with userId and date range filters, then summarise the returned events for the auditor.

Key Endpoints

1 endpoints — the hubspot cms content audit api exposes a single read endpoint for querying audit logs of cms changes that occurred on a hubspot account.

METHOD

PATH

DESCRIPTION

GET

/cms/v3/audit-logs/

Query CMS audit log events with filters

GET

/cms/v3/audit-logs/

Query CMS audit log events with filters

Why though Jentic?

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

Credential isolation

HubSpot OAuth tokens and Private App keys are stored in the Jentic encrypted vault (MAXsystem). The agent receives a scoped execution token so the raw HubSpot secret never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'hubspot cms audit log query' and receive the audit operation, its filter schema, and a ready-to-call execution wrapper.

Time to first call

Direct integration: a few hours to wire OAuth, pagination, and filter handling. Through Jentic: under 30 minutes from search to first successful call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Account Audit Logs

Account-level audit events that complement CMS-specific audit data

Use Account Audit Logs for non-CMS portal events; combine with this API for a full audit picture.

Complementary

CMS Pages

The page objects whose edits are recorded in the audit log

Use CMS Pages to read the actual page state; use this API to read the edit history.

Complementary

Blog Posts

The blog post objects whose edits are also captured in CMS audit logs

Use CMS Posts to fetch current post content; use this API to investigate who changed it.

FAQs

Specific to using CMS Content Audit API through Jentic.

What authentication does the HubSpot CMS Content Audit API use?

It accepts HubSpot OAuth 2.0 tokens or Private App tokens in the Authorization header. The audit endpoint typically requires the cms.knowledge_base or content scope on Marketing Hub Enterprise tiers; through Jentic the credentials live in the vault and the agent receives a scoped execution token.

Can the CMS Content Audit API modify or delete log entries?

No. The single endpoint GET /cms/v3/audit-logs/ is read-only. Audit records are immutable in HubSpot, which is what makes them useful as evidence.

What are the rate limits for the CMS Content Audit API?

Standard HubSpot public API limits apply: 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for Private Apps on Pro and Enterprise. Use the date filters to keep response sizes small rather than polling at high frequency.

How do I pull yesterday's CMS audit log through Jentic?

Run pip install jentic, search 'hubspot cms audit log query', load the schema, and execute it with a 24-hour date filter. Jentic handles OAuth and returns the parsed event list to the agent.

Is the HubSpot CMS Content Audit API available on every HubSpot tier?

No. CMS audit logs are an Enterprise tier feature. Calls from non-Enterprise portals return a 403 response, so check the portal level before relying on this endpoint.