HubSpot Media Bridge

Name: Media Bridge API
Brand: Media Bridge
Availability: InStock

✓ Official Vendor SpecMarketingContent Managementoauth2, apiKey32 EndpointsREST

For Agents

Register a media platform integration with HubSpot, define media object schemas, and stream playback events into HubSpot reporting on behalf of an integrator app.

Install Jentic One Beta

Connect the Media Bridge to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Media Bridge, 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.

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

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 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 Media Bridge API.

Define custom object schemas for video, audio, or other media types

Manage custom properties and property groups on media objects

GET STARTED

Start building with Media Bridge API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Media Bridge API for, with concrete tasks.

★ Connect a Video Platform to HubSpot Reporting

A video platform wants its content to appear inside HubSpot's CMS reporting alongside blog posts and pages. The Media Bridge lets the integrator register the app, define a video object schema with custom properties, and stream play events back as viewers watch. The result is unified engagement reporting without the customer leaving HubSpot.

POST to /media-bridge/v1/{appId}/settings/register with the integrator details, then create a video schema via /media-bridge/v1/{appId}/schemas and send a sample media-played-percent event.

Audio Engagement Streaming

Podcast platforms can stream attention-span and play-percent events into HubSpot so that contact records show which episodes a known listener engaged with. The events feed into HubSpot lists, workflows, and reporting just like email opens or page views, allowing audio engagement to drive lead scoring.

For each completed listening session, POST to /media-bridge/v1/events/attention-span with the contactId, mediaId, and span seconds.

Schema Migration for Existing Integrators

When an integrator changes its media data model, properties and associations on existing HubSpot media object types must be updated together. Batch archive plus property creation endpoints support a controlled migration: archive deprecated fields, register new ones, and verify via the read endpoints before the new model is used in production.

POST a list of obsolete property names to /media-bridge/v1/{appId}/properties/{objectType}/batch/archive, create the replacement properties, and confirm the changes via /media-bridge/v1/{appId}/properties/{objectType}/batch/read.

Agent-Driven Media Object Setup

An AI agent onboarding a new media partner needs to define schemas and properties without operating the HubSpot UI. Through Jentic the agent searches for the schema creation operation, loads the input shape, and executes it with the partner's media model. Subsequent property and association calls follow the same search-load-execute flow.

Use Jentic to search 'create hubspot media bridge schema', load the schema, and execute it with objectType='video' and the partner's property definitions.

Key Endpoints

32 endpoints — the hubspot media bridge api lets external media platforms register their video and audio content with hubspot so it can be embedded, tracked, and reported on alongside other cms content.

METHOD

PATH

DESCRIPTION

POST

/media-bridge/v1/{appId}/settings/register

POST

/media-bridge/v1/{appId}/schemas

Create a media object schema

POST

/media-bridge/v1/events/media-played-percent

Stream a media-played-percent event

POST

/media-bridge/v1/events/attention-span

Stream an attention-span event

POST

/media-bridge/v1/{appId}/properties/{objectType}/batch/archive

Archive properties in batch

POST

/media-bridge/v1/{appId}/properties/{objectType}/batch/read

Read properties in batch

GET

/media-bridge/v1/{appId}/settings/object-definitions

List object definitions for the integrator

POST

/media-bridge/v1/{appId}/settings/register

POST

/media-bridge/v1/{appId}/schemas

Create a media object schema

POST

/media-bridge/v1/events/media-played-percent

Stream a media-played-percent event

POST

/media-bridge/v1/events/attention-span

Stream an attention-span event

POST

/media-bridge/v1/{appId}/properties/{objectType}/batch/archive

Archive properties in batch

Why Jentic?

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

Credential isolation

HubSpot OAuth tokens, Private App tokens, and developer hapikeys 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 media bridge schema' or 'send media played percent event' and receive the matching operation plus a ready-to-execute input schema.

Time to first call

Direct integration: 3-5 days to register the app, define schemas, build event ingestion, and handle batch property updates. Through Jentic: a few hours from search to first ingested event.

FAQs

Specific to using Media Bridge API through Jentic.

What authentication does the HubSpot Media Bridge API use?

It accepts HubSpot OAuth 2.0 tokens or Private App tokens in the Authorization header, plus a developer hapikey query parameter for some integrator-management endpoints. Jentic stores both forms in its vault and exposes only a scoped execution token to the agent.

Can I store the actual video file in the Media Bridge?

No. The Media Bridge stores metadata, properties, and engagement events about media that lives on the integrator's platform. Video and audio bytes remain on the integrator's CDN; HubSpot only references them by ID.

What are the rate limits for the Media Bridge API?

It shares 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. High-volume event ingestion should be batched where possible to stay under those limits.

How do I send a play event for a specific viewer through Jentic?

Run pip install jentic, search 'send hubspot media played percent event', load the schema, and execute it with the viewer's contactId, the mediaId, and the percentage played. Jentic posts to /media-bridge/v1/events/media-played-percent with the right auth headers.

Does the Media Bridge support custom event types beyond play percent and attention span?

Not in this spec. The two ingestion endpoints exposed are media-played-percent and attention-span. For richer behavioural tracking, pair Media Bridge with HubSpot's Custom Events API, which supports arbitrary event definitions.

HubSpot Media Bridge

Connect the Media Bridge to your agent

Capabilities

Start building with Media Bridge API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs