How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Megaphone Episodes API

Episodes within a podcast, including dynamic ad insertion.

Megaphone Episodes API is one of 7 APIs that Megaphone publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Episodes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 2.0.

Requests are made against 2 base URLs: https://cms.megaphone.fm/api, https://cms.megaphone.fm/api/v2.

5 operations 2 paths 2 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0
Base URL
https://cms.megaphone.fm/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Megaphone Episodes API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (tokenAuth). By default, every request must be authenticated.

  • tokenAuth — Per-user API token sent as Authorization: Token token=" ". Generated on account creation and managed under User Settings; treat as a password and do not reuse…

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Episodes 5

Episodes within a podcast, including dynamic ad insertion.

GET
/networks/{network_id}/podcasts/{podcast_id}/episodes
List episodes in a podcast
listEpisodes 5 params → 200401429
POST
/networks/{network_id}/podcasts/{podcast_id}/episodes
Create an episode
createEpisode 2 params body → 201401
GET
/networks/{network_id}/podcasts/{podcast_id}/episodes/{episode_id}
Retrieve an episode
getEpisode 3 params → 200401
PUT
/networks/{network_id}/podcasts/{podcast_id}/episodes/{episode_id}
Update an episode
updateEpisode 3 params body → 200401
DELETE
/networks/{network_id}/podcasts/{podcast_id}/episodes/{episode_id}
Delete an episode
deleteEpisode 3 params → 204401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Episode (11 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Episode
object
An episode within a podcast, including dynamic ad insertion configuration.
11 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

megaphone-episodes-api-openapi.yml Raw ↑

Other APIs Megaphone publishes across the network.

Megaphone Campaigns API
Megaphone Direct Sales v2 API
Megaphone Exports API
Megaphone Networks API
Megaphone Orders API
Megaphone Podcasts API
Where this information came from

This is an independent, third-party profile of Megaphone Episodes API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.