Retrieve media metadata and playback manifests using the JW Player Delivery API v2
domain: docs.jwplayer.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For public/unsigned media, call GET https://cdn.jwplayer.com/v2/media/{media_id} to retrieve metadata, images, tracks, conversions, and manifests
If referencing content by an external ID instead of JW Player's internal media ID, use GET https://cdn.jwplayer.com/v2/site/{site_id}/media/ext:{external_id}
For management-style listing/creation (not just delivery), use the api.jwplayer.com/v2/sites/{site_id}/media/ endpoints instead of the cdn delivery host
Request the response in JSON or one of the supported RSS formats depending on the consuming system
Cache delivery responses appropriately since the Delivery API is meant for viewer-facing playback, not bulk management
Known gotchas
Delivery API calls go to the cdn.jwplayer.com host while management-style calls go to api.jwplayer.com - mixing them up is a common integration mistake
Management API media listing is capped at 10,000 objects per request, so bulk exports need pagination/batching logic
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?