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

Magnifi Partner Integration API

Partner REST API for Magnifi by VideoVerse. Partners authenticate with an Access Key and Access Secret pair (x-access-key / x-access-secret headers) and use the API to ingest live or recorded streams (HLS, RTMP, SRT, MP4), read the AI-generated clips, highlights and highlight clips produced from them, export match videos, manage tournament / team / player rosters and match schedules, fetch pre-signed content URLs, manage entity members, and subscribe to change notifications over webhooks. The base URL is issued to each partner with their credentials and is not published, so the contract carries it as the templated server {PARTNER_BASE_URL}.

This API exposes 57 operations across 42 paths, organized into 14 resource areas, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version v1.

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

57 operations 42 paths 2 schemas 3 DELETE35 GET3 PATCH12 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

Magnifi Partner Integration 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 57

Across 42 paths, the API surfaces 57 operations — 3 DELETE, 35 GET, 3 PATCH, 12 POST, 4 PUT. They span 14 resource areas, including Partner, Streams, Clips, Highlights, Highlight Clips, Match Video, Content, Player, and 6 more. Each is listed below with its method, path, parameters, and response codes.

Partner 10
GET
/v1/partner/details
Get Partner Details
getPartnerDetails → 200401default
GET
/v1/partner/categories
Get Partner Categories
getPartnerCategories 2 params → 200401default
GET
/v1/partner/templates
Get Partner Templates
getPartnerTemplates → 200401default
GET
/v1/partner/workspaces
Get Partner Workspaces
getPartnerWorkspaces → 200404401default
GET
/v1/partner/stream-fields
Get Partner Stream Custom Fields
getPartnerStreamCustomFields 1 param → 200401default
GET
/v1/partner/clip-naming-templates
Get Partner Clip Naming Templates
getPartnerClipNamingTemplates → 200401default
GET
/v1/partner/storage-buckets
Get Partner Storage Buckets
getPartnerStorageBuckets → 200401default
GET
/v1/partner/languages
Get Partner Languages
getPartnerLanguages → 200401default
GET
/v1/partner/audio-options
Get Partner Template Audio Options
getPartnerTemplateAudioOptions → 200401default
POST
/v1/partner/getPreSignedUrldeprecated
Generate Pre-signed Url (to be deprecated)
generatePreSignedUrl body → 200404401default
Streams 9
POST
/v1/stream
Create stream
createStream body → 202400401default
GET
/v1/stream
Get all streams
getAllStreams 6 params → 200401default
PATCH
/v1/stream/{streamId}
Update stream by streamId
updateStreamByStreamId 1 param → 200401default
GET
/v1/stream/{streamId}
Get stream by streamId
getStreamByStreamId 1 param → 200404401default
GET
/v1/stream/{streamId}/clips
Get clips by streamId
getClipsByStreamId 3 params → 200404401default
GET
/v1/stream/{streamId}/hlclips
Get hlClips by streamId
getHlClipsByStreamId 3 params → 200401default
GET
/v1/stream/{streamId}/highlights
Get highlights by streamId
getHighlightsByStreamId 3 params → 200404401default
GET
/v1/stream/{streamId}/filters
Get filters by streamId
getFiltersByStreamId 1 param → 200401default
GET
/v1/stream/{streamId}/match-videos
Get Match Videos by streamId
getMatchVideosByStreamId 4 params → 200401default
Clips 1
GET
/v1/clip/{clipId}
Get by clipId
getByClipId 1 param → 200404401default
Highlights 1
GET
/v1/highlight/{highlightId}
Get Highlight by highlightId
getHighlightByHighlightId 1 param → 200500404401default
Highlight Clips 1
GET
/v1/hlclip/{hlclipId}
Get hlClip by hlclipId
getHlClipByHlclipId 1 param → 200404401default
Match Video 2
GET
/v1/match-video/{matchVideoId}
Get match video by matchVideoId
getMatchVideoByMatchVideoId 1 param → 200401default
GET
/v1/match-video
Get all match videos
getAllMatchVideos 6 params → 200401default
Content 1
POST
/v1/content/presigned-url
Fetch Presigned Url
fetchPresignedUrl body → 200401default
Player 4
POST
/v1/partner/player
Add player
addPlayer body → 201401default
GET
/v1/partner/player
Get all players
getAllPlayers 2 params → 201200401default
PUT
/v1/partner/player/{playerId}
Update player by playerId
updatePlayerByPlayerId 1 param body → 200401default
GET
/v1/partner/player/{playerId}
Get player by playerId
getPlayerByPlayerId 1 param → 200401default
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
Tournament 4
POST
/v1/partner/tournament
Add tournament
addTournament body → 201401default
GET
/v1/partner/tournament
Get all tournaments
getAllTournaments 2 params → 200401default
PUT
/v1/partner/tournament/{tournamentId}
Update tournament by tournamentId
updateTournamentByTournamentId 1 param body → 200401default
GET
/v1/partner/tournament/{tournamentId}
Get tournament by tournamentId
getTournamentByTournamentId 1 param → 200401default
Match Schedule 7
POST
/v1/match-schedule
Create match schedule
createMatchSchedule body → 201400401default
GET
/v1/match-schedule
Get all match schedules
getAllMatchSchedules 2 params → 200401default
PATCH
/v1/match-schedule/{matchScheduleId}
Update match schedule by matchScheduleId
updateMatchScheduleByMatchScheduleId 1 param body → 200404401default
GET
/v1/match-schedule/{matchScheduleId}
Get match schedule by matchScheduleId
getMatchScheduleByMatchScheduleId 1 param → 200404401default
DELETE
/v1/match-schedule/{matchScheduleId}
Delete match schedule by matchScheduleId
deleteMatchScheduleByMatchScheduleId 1 param → 200401default
POST
/v1/match-schedule/{matchScheduleId}/de-link
De-link by matchScheduleId
deLinkByMatchScheduleId 1 param → 200404401default
POST
/v1/match-schedule/{matchScheduleId}/invoke-stream
Invoke stream by matchScheduleId
invokeStreamByMatchScheduleId 1 param body → 202400401default
Catch me up 1
GET
/v1/catch-me-up/highlight
Get Catch me up Highlight
getCatchMeUpHighlight 2 params → 200404401default
Webhook 6
GET
/v1/webhook/notifier/topics
Fetch Topics
fetchTopics → 200401default
POST
/v1/webhook/notifier/subscription
Create Subscription
createSubscription body → 201401default
PATCH
/v1/webhook/notifier/subscription/{subscriptionId}
Update Subscription
updateSubscription 1 param body → 200401default
GET
/v1/webhook/notifier/subscription/{subscriptionId}
Get Subscription by subscriptionId
getSubscriptionBySubscriptionId 1 param → 200400401default
DELETE
/v1/webhook/notifier/subscription/{subscriptionId}
Delete Subscription
deleteSubscription 1 param → 204401default
GET
/v1/webhook/notifier/subscriptions
Get Subscriptions
getSubscriptions → 200401default
Entity Member 6
POST
/v1/entity-member
Create Entity Member
createEntityMember body → 200401default
GET
/v1/entity-member
Get Entity Members
getEntityMembers → 200401default
POST
/v1/entity-member/assign
Assign Role to User
assignRoleToUser body → 200401default
GET
/v1/user/assignable
Get Assignable Users
getAssignableUsers → 200401default
PUT
/v1/entity-member/{entityMemberId}
Update Entity Member Role
updateEntityMemberRole 1 param body → 200401default
DELETE
/v1/entity-member/{entityMemberId}
Remove Entity Member
removeEntityMember 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-magnifi-partner-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Magnifi Partner Integration 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.