The API Report CardAPI Index
THE API REPORT CARD / Software & Data Tools / Brightcove
Brightcove

Brightcove API

brightcove.com

A comprehensive set of REST APIs covers the whole video stack: CMS, ingest, playback, analytics, live, SSAI, and player management, with OAuth2 and native SDKs. Access is sales-gated with no self-serve tier, and the surface sprawls across 17-plus services with inconsistent conventions.

Last verified: July 2026Software & Data Tools
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST APIs cover the full video stack: CMS, ingest, playback, analytics, live, SSAI, and player management.
AccessPOORSales-gated at the commercial tier; full Studio and API provisioning requires sales engagement, not signup.
CoverageMIXEDNearly every media operation is reachable, but across 17-plus services with inconsistent hosts and response shapes.
AuthGOODOAuth2 client-credentials grant with per-resource, per-operation scopes and bearer tokens.
Docs & DXGOODA full public portal with per-service references, sample payloads, and native player SDKs for iOS, Android, and TV.
StabilityMIXEDAn April 2025 CMS API incident cascaded into Studio and Distribution for two days; player publishes can serve stale caches.
MORE FROM THE REPORT CARD
KalturaAMuxAWistiaD+VidyardC+
Supergood: Brightcove has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Brightcove scores C on the API Report Card. A comprehensive set of REST APIs covers the whole video stack: CMS, ingest, playback, analytics, live, SSAI, and player management, with OAuth2 and native SDKs. Access is sales-gated with no self-serve tier, and the surface sprawls across 17-plus services with inconsistent conventions.

Tried to integrate with Brightcove?
SOURCES
CMS API endpoint reliability incident April 14-15 2025, a specific CMS API endpoint responsible for returning 'clear' content URLs experienced delays and intermittent errors, cascading into Video Cloud Studio UI, the Social module, and Distribution over two days isdown.app ↗
No publicly documented per-API rate limits, Brightcove's Analytics API is documented as supporting 100,000+ daily requests but per-second / per-minute ceilings for CMS, Dynamic Ingest, Playback, and other APIs are not published, so integrators discover throttling via 429s in production apis.support.brightcove.com ↗
Sprawling API surface (CMS + Dynamic Ingest + Playback + Image + Analytics + Audience + Social + Live + NextGen Live 2.0 + SSAI + Player Management + Policy + Delivery Rules + Delivery System + Ingest Profiles + Cloud Playout + Playback Restrictions + OAuth) with inconsistent base hosts, response shapes, and version conventions across services apis.support.brightcove.com ↗
OAuth2 scope strings are fine-grained and brittle, issuing a single client credential that spans CMS + Dynamic Ingest + Playback + Analytics + Player Management requires composing a long space-separated scope list, and missing one operation silently 401s in production apidocs.brightcove.com ↗
Webhook (Notifications) catalog is split across Dynamic Ingest callbacks, Live state events, and CMS notifications with different payload conventions per service; integrators have to assemble a coherent media-lifecycle picture across three notification streams apis.support.brightcove.com ↗
Player Management API versioning creates cache invalidation surprises, publishing a player version requires explicit publish steps and old cached versions can serve until propagation completes apis.support.brightcove.com ↗
Live and NextGen Live 2.0 are two parallel live-streaming API surfaces, Brightcove documents migration paths but mixed-version codebases in the wild are common apis.support.brightcove.com ↗
SSAI and ad-stack failures (VAST timeouts, malformed creatives, blocked categories) frequently degrade silently, without explicit instrumentation, ad ops teams notice via revenue dips rather than error logs apis.support.brightcove.com ↗
No widely indexed public status / SLA page equivalent to status.stripe.com, uptime is tracked by third-party monitors (StatusGator, IsDown, SaaSHub, Downosaur) rather than a first-party real-time status feed that customers can subscribe to statusgator.com ↗
Dynamic Ingest multipart upload (>50GB) is a multi-step orchestration (request upload URL → multipart PUT → notify completion) that fails silently if any step is skipped or out of order apis.support.brightcove.com ↗
Bending Spoons-era support / engineering cuts have lengthened time-to-response on API-incident escalations, Aragon Research and TVBEurope coverage explicitly tie the layoffs to a 'maintenance-mode' platform posture aragonresearch.com ↗
Documentation URL churn across apis.support.brightcove.com, apidocs.brightcove.com, support.brightcove.com, and players.brightcove.net has occasionally broken deep links and integration documentation references apis.support.brightcove.com ↗
Pricing is opaque and expensive, no public self-serve pricing; G2 reviews cite plans starting ~$200/month with combined website-builder + Brightcove pricing escalating quickly; smaller orgs frequently churn out over cost g2.com ↗
User interface is clunky and not intuitive, reviewers describe difficulty navigating, searching, and organizing content in Studio; recurring ask for a more modern, manageable UX g2.com ↗
Reporting / analytics lacks specificity and delivery is delayed, reports are not granular enough and there are documented lags before data is available g2.com ↗
Bending Spoons-era support degradation, following the Feb 4 2025 acquisition, Bending Spoons laid off 198 Boston-HQ employees within ~6 weeks (reported as two-thirds of U.S. staff, with industry coverage and Hacker News accounts citing 85%+ of total Brightcove staff), gutting customer success, support, and platform engineering boston.com ↗
Aragon Research and TVBEurope flagged the Vimeo + Brightcove cuts as a 'maintenance-mode' shift signaling reduced product investment under Bending Spoons' standard playbook of aggressive cost-cutting aragonresearch.com ↗
Customer-impacting CMS API incident April 14-15 2025, Brightcove status / IsDown / StatusGator monitoring captured a multi-day issue affecting CMS API responses (specifically the endpoint returning 'clear' content URLs) that cascaded into Video Cloud Studio UI, then the Social module, then Distribution; resolution required narrowing scope across two days isdown.app ↗
Brightcove Distribution warning of 18h 35m on August 29, 2025 captured by StatusGator statusgator.com ↗
StatusGator has tracked 1,238+ outages affecting Brightcove users across ~11 years of monitoring statusgator.com ↗
Capterra / SoftwareAdvice / PeerSpot reviews echo concerns about UI complexity, admin overhead, and a product surface (Video Cloud + Beacon + Cloud Playout + Live + NextGen Live + Interactivity + Gallery + Marketing Studio + Communications Studio) that has grown faster than the underlying admin tooling can keep up with softwareadvice.com ↗
Customers frequently evaluate Wistia, Vimeo, Vidyard, Kaltura, JW Player, Mux, and Dacast specifically because of cost and interface friction at Brightcove g2.com ↗
Glassdoor reviews from inside the company post-acquisition describe a depressed culture and concern about long-term platform investment under Bending Spoons glassdoor.com ↗
© Supergood Systems, Inc.