Hubhopper Partner Integration API(s) - Production

Name: Hubhopper Partner Integration API(s) - Production API
Brand: Hubhopper Partner Integration API(s) - Production
Availability: InStock

✓ Official Vendor SpecMediaAudio ProcessingapiKey7 EndpointsREST

For Agents

Browse the Hubhopper podcast catalogue by category, retrieve podcast metadata, and list episodes for use in directory or discovery experiences.

Install Jentic One Beta

Connect the Hubhopper Partner Integration API(s) - Production to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hubhopper Partner Integration API(s) - Production, 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 Hubhopper Partner Integration API(s) - Production API.

List the podcast categories available to a Hubhopper partner

Retrieve a single category by id with its display metadata

List the podcasts that belong to a specific category

GET STARTED

Start building with Hubhopper Partner Integration API(s) - Production API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Hubhopper Partner Integration API(s) - Production API for, with concrete tasks.

★ Power a partner podcast directory page

A partner site that surfaces podcasts to its users can render category pages, podcast detail pages, and episode lists from the Hubhopper API. GET /categories drives the navigation, GET /categories/{categoryId}/podcasts populates each category page, and GET /podcasts/{podcastId}/episodes loads the episode list for a podcast detail page. The hhPartnerId header scopes results to the partner's licensed catalogue.

Call GET /categories to render navigation, then GET /categories/{categoryId}/podcasts to populate the page for the selected category

Fetch episode metadata for a podcast player

An audio player surfaces the episode list and metadata for a podcast the user clicked on. GET /podcasts/{podcastId} returns the podcast's title, description, and image, and GET /podcasts/{podcastId}/episodes returns the episode list with publish dates and audio references. Together they fully populate a player view without scraping.

Call GET /podcasts/{podcastId} for the header metadata and GET /podcasts/{podcastId}/episodes for the playable episode list

Localise the catalogue by language

Apps targeting specific Indian-language audiences can use GET /util/languages to list supported language codes, then filter podcast browsing accordingly. The languages endpoint is the source of truth for valid locale values that appear elsewhere in the catalogue.

Call GET /util/languages and store the supported language codes for use as filters in the partner UI

Agent integration via Jentic

A content-recommendation agent can fetch fresh podcast metadata for a user query without managing API keys directly. The agent searches Jentic for the catalogue operation, loads the schema, and executes the call. The Hubhopper x-api-key and hhPartnerId stay encrypted in the Jentic vault.

Search Jentic for 'list hubhopper podcasts in a category', load the schema for GET /categories/{categoryId}/podcasts, and execute with the chosen categoryId

Key Endpoints

7 endpoints — the hubhopper partner integration api gives partner platforms read access to the hubhopper podcast catalogue, exposing categories, podcasts, episodes, and supported languages.

METHOD

PATH

DESCRIPTION

GET

/categories

List all podcast categories

GET

/categories/{categoryId}

Retrieve a single category

GET

/categories/{categoryId}/podcasts

List podcasts in a category

GET

/podcasts

List the partner-allowed podcast catalogue

GET

/podcasts/{podcastId}

Retrieve podcast metadata

GET

/podcasts/{podcastId}/episodes

List episodes for a podcast

GET

/util/languages

List supported languages

GET

/categories

List all podcast categories

GET

/categories/{categoryId}

Retrieve a single category

GET

/categories/{categoryId}/podcasts

List podcasts in a category

GET

/podcasts

List the partner-allowed podcast catalogue

GET

/podcasts/{podcastId}

Retrieve podcast metadata

Why Jentic?

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

Credential isolation

Hubhopper x-api-key and hhPartnerId values are stored encrypted in the Jentic vault. Agents call /partner endpoints through scoped session tokens and never see the raw partner key.

Intent-based discovery

Agents search Jentic with intents like 'list podcasts in a hubhopper category' and Jentic returns the matching GET /categories/{categoryId}/podcasts operation with its input schema.

Time to first call

Direct integration: a few hours to wire the dual-header auth and pagination handling. Through Jentic: under an hour — search, load, execute against the seven read endpoints.

FAQs

Specific to using Hubhopper Partner Integration API(s) - Production API through Jentic.

What authentication does the Hubhopper Partner API use?

The spec defines two apiKey schemes that are used together: x-api-key in the request header for the partner API key, and hhPartnerId in the request header to identify the partner account. Both must be present on every call. Through Jentic these credentials are stored encrypted in the vault.

Can I list podcasts within a specific category with the Hubhopper API?

Yes. GET /categories/{categoryId}/podcasts returns the podcasts that belong to a given category, scoped to the partner catalogue identified by the hhPartnerId header. Use GET /categories first to discover valid category ids.

What are the rate limits for the Hubhopper Partner API?

The spec does not publish an explicit rate limit. Hubhopper sets per-partner quotas at provisioning time, so contact your Hubhopper partner manager to confirm the cap on x-api-key calls per minute for your account.

How do I list podcasts through Jentic?

Search Jentic for 'list podcasts in a hubhopper category', load the schema for GET /categories/{categoryId}/podcasts, and execute with the chosen categoryId. Jentic returns the JSON list of podcasts with their metadata.

Is the Hubhopper Partner API free?

The Partner Integration API is gated by a partner agreement with Hubhopper. Pricing is negotiated per partner and is not exposed in the spec — request access by contacting Hubhopper directly.

Can I create or upload podcasts with this API?

No. All seven endpoints are GET requests. The Partner Integration API is read-only and is intended for distribution and discovery rather than catalogue management.