REST API

Every Library is an API. All read access to published content is anonymous — no API key, no sign-up (the whole auth story fits in auth.md). Published episodes are readable; unpublished ones 404.

The versioned surface is /api/v1. Every documented endpoint is a read-only GET — idempotent and safe to retry — and errors are always JSON with an error message, never HTML. A breaking change would ship as /api/v2, with Deprecation and Sunset headers on the retiring version.

Search a channel

Hybrid (semantic + keyword) search over a channel's published episodes:

curl "https://podhood.com/api/v1/channels/{slug}/search?query=pricing%20strategy"

const res = await fetch("https://podhood.com/api/v1/channels/{slug}/search?query=pricing+strategy");
const { episodes } = await res.json();

import requests

res = requests.get(
    "https://podhood.com/api/v1/channels/{slug}/search",
    params={"query": "pricing strategy"},
)
episodes = res.json()["episodes"]

Facet filters accept comma-separated ids: topicIds, personIds, entityIds, episodeIds — plus collectionId and year. Pass fast=true for keyword-only search.

Browse episodes

A keyset-paginated list of published episodes, with the same facet filters plus sort:

curl "https://podhood.com/api/v1/channels/{slug}/episodes"

Pass the response's nextCursor back as cursor for the next page.

Episode resources

GET /api/v1/episodes/{episodeId}/transcript   # word-level transcript
GET /api/v1/episodes/{episodeId}/chapters     # chapters with key moments
GET /api/v1/episodes/{episodeId}/related      # topically related episodes

Markdown for agents

Beyond JSON, every episode and marketing page has a Markdown twin — append .md to the URL, or send Accept: text/markdown. Each host also serves llms.txt as its machine-readable index, and /.well-known/api-catalog for programmatic discovery.

If your agent speaks MCP, the per-channel MCP server is usually the better interface: one search tool, citation URLs included.