Hubhopper Partner Integration API(s) - Production
22
AI ReadinessNon-Ready (F)22/100
Official vendor OpenAPI document · agent-readyMediaAudio ProcessingapiKey7 EndpointsREST
For Agents
Browse the Hubhopper podcast catalogue by category, retrieve podcast metadata, and list episodes for use in directory or discovery experiences.
Use for: I need to list all podcast categories available to my partner account, Get the podcasts in the news category, Retrieve metadata for podcast id abc123, List all episodes of a specific podcast
Not supported: Does not upload podcasts, manage subscriptions, or stream audio - use only to read partner-licensed Hubhopper catalogue data such as categories, podcasts, and episodes.
The Hubhopper Partner Integration API gives partner platforms read access to the Hubhopper podcast catalogue, exposing categories, podcasts, episodes, and supported languages. Partners can list and browse categories, list podcasts within a category, fetch the metadata for a specific podcast, and pull the episode list for that podcast. Authentication uses an x-api-key header alongside an hhPartnerId header that scopes the response to the partner's allowed catalogue. The API is read-only and is intended for podcast directory and discovery integrations.
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.
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%2Fhubhopper.com%2Fhubhopper" | 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%2Fhubhopper.com%2Fhubhopper" | 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 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
Browse the full partner-allowed podcast catalogue with pagination
Fetch the metadata for a single podcast by podcast id
Retrieve the episode list for a podcast
Look up the supported languages for filtering podcast results
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 your Jentic One instance.
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
GET
/podcasts/{podcastId}/episodes
List episodes for a podcast
GET
/util/languages
List supported languages
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.
H
Hubhopper Partner Integration API(s) - Production
- Non-Ready (F)22/100
93
Foundational Compliance69
Developer Experience & Jentic Compatibility7
AI-Readiness & Agent Experience94
Agent Usability50
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
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.
7
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
28%
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.
0%
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
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 the Hubhopper Partner Integration API by hand means sending both the x-api-key and hhPartnerId headers on every call to apis.hubhopper.com/partner and paging the catalogue records yourself. Through Jentic you install once, import the Hubhopper Partner Integration API from the API Directory, store the partner key once, and your agent calls it.
Permission scoping
Hubhopper puts the category and podcast ids in the URL path (/categories/{categoryId}, /podcasts/{podcastId}), so a rule can pin your agent to reading one category or podcast and nothing else. Every operation here is read-only, so the agent has no write or delete calls to grant.
Credential isolation
Your Hubhopper x-api-key and hhPartnerId are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list podcasts in a hubhopper category', and Jentic returns GET /categories/{categoryId}/podcasts 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 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.
Can I limit what my agent is allowed to do with the Hubhopper Partner API?
Yes. Because you run Jentic One yourself, your own rules decide which Hubhopper operations and credentials the agent may use. Every endpoint here is read-only, so there are no write or delete calls to grant, and since the category and podcast ids sit in the URL path (/categories/{categoryId}, /podcasts/{podcastId}), a rule can pin the agent to reading a single category or podcast and nothing else. Your x-api-key and hhPartnerId stay with your instance and are injected only when an allowed call runs.
GET STARTED