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

Brightcove Schedule SEP Job Start Stop API

Operations for scheduling the activation and deactivation of an SEP job.

Brightcove Schedule SEP Job Start Stop API is one of 53 APIs that Brightcove publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Schedule SEP Job Start Stop. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against a single base URL, https://api.bcovlive.io/v1.

4 operations 2 paths 5 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://cms.api.brightcove.com/v1
Resource Areas
1

Paths & Operations 4

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

Schedule SEP Job Start Stop 4

Operations for scheduling the activation and deactivation of an SEP job.

POST
/scheduler/jobstartstop
Create a JobStartStop workflow to schedule activation/deactivation of an SEP job
CreateAJobStartStop 2 params body → 200400401404500
GET
/scheduler/jobstartstop/{workflow_id}
Get JobStartStop Details
GetJobStartStop 3 params → 200401404500
PUT
/scheduler/jobstartstop/{workflow_id}
Update JobStartStop Details
UpdateJobStartStop 3 params body → 200401404500
DELETE
/scheduler/jobstartstop/{workflow_id}
Cancel JobStartStop
CancelJobStartStop 3 params → 200401404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are JobStartStop (8 properties), CreateJobStartStopRequestBody (6 properties), JobStartStop.TaskInfo (3 properties), UpdateJobStartStopRequestBody (2 properties). Each schema is shown below with its type and property counts.

CreateJobStartStopRequestBody.TaskInfo
object
2 properties 1 required
CreateJobStartStopRequestBody
object
6 properties 3 required
UpdateJobStartStopRequestBody
object
2 properties
JobStartStop.TaskInfo
object
3 properties 2 required
JobStartStop
object
8 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brightcove-schedule-sep-job-start-stop-api-openapi.yml Raw ↑

Other APIs Brightcove publishes across the network.

Brightcove Dynamic Ingest API
Brightcove Analytics API
Brightcove Playback API
Brightcove Player Management API
Brightcove Live API
Brightcove OAuth API
Brightcove SSAI API
Brightcove Ingest Profiles API
Brightcove Delivery Rules API
Brightcove Cloud Playout APIs
Brightcove Audience API
Brightcove Social API
Where this information came from

This is an independent, third-party profile of Brightcove Schedule SEP Job Start Stop 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.