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

Coactive video-scores > videoScores API

The video-scores > videoScores API from Coactive — 4 operation(s) for video-scores > videoscores.

Coactive video-scores > videoScores API is one of 22 APIs that Coactive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include video-scores > videoScores. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

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

Requests are made against 2 base URLs: https://api.coactive.ai, https://app.coactive.ai.

4 operations 4 paths 19 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.coactive.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Coactive video-scores > videoScores API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 4

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

video-scores > videoScores 4
GET
/api/v0/video-scores/groups/{group_id}/tags/{tag_id}/versions/{version_id}/videos/{video_id}/shot-scores
Get shot scores for a video
get-video-shot-scores 7 params → 200404422
GET
/api/v0/video-scores/groups/{group_id}/tags/{tag_id}/aggregations/{aggregation_id}/result
Get video scores result
get-video-scores-result 7 params → 200422
GET
/api/v0/video-scores/groups/{group_id}/tags/{tag_id}/aggregations/{aggregation_id}/result/count
Get video scores result count
get-video-scores-result-count 6 params → 200422
GET
/api/v0/video-scores/groups/{group_id}/tags/{tag_id}/aggregations/-/result
Get video scores result preview
get-video-scores-result-preview 10 params → 200400422

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are video-scores_VideoScore (15 properties), video-scores_VideoModel (10 properties), video-scores_VideoMetadata (7 properties), video-scores_ShotScore (6 properties). Each schema is shown below with its type and property counts.

video-scores_VideoModel
object
Video details.
10 properties 8 required
video-scores_PageDetails
object
Pagination metadata.
2 properties 2 required
video-scores_ShotScore
object
Shot-level score for a single shot in a video (only shots meeting minconf are returned).
6 properties 5 required
video-scores_GetVideoShotScoresResponse
object
Response for getting shot scores for a video.
2 properties
video-scores_ValidationErrorLocItems
video-scores_PageMetadata
object
Metadata about the paginated response.
2 properties 2 required
video-scores_GetVideoScoresResponse
object
Response for getting video scores.
3 properties 1 required
video-scores_SortDirection
string
Sort direction for results.
video-scores_SortField
object
Sort field details.
2 properties 1 required
video-scores_VideoMetadata
object
Video metadata from the metadata service.
7 properties
video-scores_VideoScore
object
Video score result.
15 properties 10 required
video-scores_HTTPValidationError
object
1 property
video-scores_ShotTextPrompt
object
Text prompt with modality information for shot scoring.
2 properties 2 required
video-scores_VideoModelInternalMetadata
object
video-scores_GetVideoScoresResultCountResponse
object
Response for getting video scores result count.
5 properties 5 required
video-scores_AggregationEngine
string
Backend engine used to query shot scores. DUCKDB (default) supports all aggregation strategies; PINOT supports ANYHIT and COVERAGETHRESHOLD only.
video-scores_GetVideoScoresResultCountPredicate
object
Predicate used for counting video scores.
2 properties 1 required
video-scores_AggregationMethodology
string
The methodology used for aggregating shot scores into video scores. LONGESTRUN is only supported with the DUCKDB engine.
video-scores_ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coactive-video-scores-videoscores-api-openapi.yml Raw ↑

Other APIs Coactive publishes across the network.

Coactive agentic-search > agenticSearch API
Coactive celebrity-detection API
Coactive classification API
Coactive concept API
Coactive connections > connections API
Coactive context-studio > adSegments API
Coactive datasets > dataset API
Coactive datasets > datasetConfig API
Coactive datasets > encoder API
Coactive dynamicTags API
Coactive ingestion API
Coactive ingestion > ingest API
Where this information came from

This is an independent, third-party profile of Coactive video-scores > videoScores 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.