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

VideoVerse Team API

The Team API from VideoVerse — 2 operation(s) for team.

VideoVerse Team API is one of 14 APIs that VideoVerse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Team. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

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

Requests are made against a single base URL, {PARTNER_BASE_URL}.

4 operations 2 paths 2 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Server
{PARTNER_BASE_URL}
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

VideoVerse Team API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-access-key (AccessKey). An API key is passed in the header as x-access-secret (AccessSecret). By default, every request must be authenticated.

  • AccessKey — Partner Access Key issued by Magnifi. Documented example prefix: pak.
  • AccessSecret — Partner Access Secret issued by Magnifi. Sent on every request alongside x-access-key.

Paths & Operations 4

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

Team 4
POST
/v1/partner/team
Add team
addTeam body → 201401default
GET
/v1/partner/team
Get all teams
getAllTeams 2 params → 200401default
PUT
/v1/partner/team/{teamId}
Update team by teamId
updateTeamByTeamId 1 param body → 200401default
GET
/v1/partner/team/{teamId}
Get team by teamId
getTeamByTeamId 1 param → 200401default

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are AuthError (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

AuthError
object
Returned when the access key or secret is missing or invalid.
3 properties
Error
object
Magnifi error envelope. error.code is a Magnifi error code (see errors/videoverse-problem-types.yml).
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

videoverse-team-api-openapi.yml Raw ↑

Other APIs VideoVerse publishes across the network.

VideoVerse Catch me up API
VideoVerse Clips API
VideoVerse Content API
VideoVerse Entity Member API
VideoVerse Highlight Clips API
VideoVerse Highlights API
VideoVerse Match Schedule API
VideoVerse Match Video API
VideoVerse Partner API
VideoVerse Player API
VideoVerse Streams API
VideoVerse Tournament API
Where this information came from

This is an independent, third-party profile of VideoVerse Team 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.