All Products API Overview

Copy

Muvi APIs are organized by product so developers can quickly find the right endpoints for their use case.

This portal currently covers:

• Muvi One: OTT/content platform APIs (content, billing, users, monetization).
• Muvi Flex: CMS/site and product management APIs for flexible web/app experiences.
• Muvi Playout: channel scheduling, playout control, ad insertion, and related operations.
• Muvi Live: livestream/session APIs and live infrastructure-related operations.
• Muvi Meet: Meet APIs and meeting-related operations.
• Muvi Player: player SDK and playback-related integrations.

Quick Start

1. Select your product from Products.
2. Open Introduction for that product to understand prerequisites.
3. Pick an endpoint from API categories and test with your token.

How APIs Are Structured

• Endpoint: route and method (GET, POST, PUT, DELETE, etc.).
• Headers: required auth and content-type details.
• Request Parameters: input fields with type/required status.
• Request Example: sample payload or query.
• Response Fields/Examples: success and failure response formats.

Common Parameters You Will See

• app_token: unique application token.
• product_key: product identifier for the current API context.
• store_key: account/store key (required in specific product flows).
• user_uuid: end-user or account user identifier.

Product Selection Guidance

Recommended Developer Flow

• Start from All Products to understand platform scope.
• Switch to your product and review its Introduction first.
• Validate one API end-to-end (request + response) before bulk integration.
• Reuse shared patterns (headers, error handling, auth lifecycle) across endpoints.

Notes

• Endpoint availability can vary by product and account configuration.
• Some routes may use REST while others follow GraphQL query patterns.
• Always validate against your active environment before production rollout.