Ingest a video into Brightcove using Dynamic Ingest API
domain: apis.support.brightcove.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate by obtaining a temporary access token from the Brightcove OAuth API using your client credentials (client_id and client_secret) with the dynamic-ingest write scope.
Create a video object in your Brightcove Video Cloud account by sending a POST request to the CMS API videos endpoint with at minimum a name field.
Note the video id returned in the response.
Construct a Dynamic Ingest request payload with a master object containing the url of the source video file (publicly accessible) and optionally a profile name.
POST the ingest payload to the Dynamic Ingest API ingestion endpoint for the video id.
Monitor ingest progress via Brightcove's notification system or by polling the CMS API for the video's status.
Known gotchas
Access tokens from the Brightcove OAuth service are short-lived (typically 5 minutes); request a fresh token for each ingest job rather than reusing cached tokens.
The source video URL must be publicly accessible without authentication at the time Brightcove's ingest system fetches it; pre-signed URLs that expire quickly may cause ingest failures.
Dynamic Ingest does not return a synchronous result; use Brightcove's notification callbacks or polling to determine when the video is ready.
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?