StreamAMG Fusion

Introduction

Features

Client Guides

Exporting Reports

Creating a PPV Package

Creating a Recurring Subscription Package

FeatureIDs & Adding an Entitlement to Video Content

Putting a Package on-sale/off-sale

Customer Profiles, Refunds, Cancellations

Complementary Subscriptions

Integration Guides

Creating a Simple Checkout

Customer Portal Flow

Building a Pricing Table

Migration from CloudPay to Fusion + Stripe Checkout

FAQ's

Creating Products in Stripe

<p class="slate-p " >API for managing monetization operations and proxying Stripe calls.</p><p class="slate-p " ><strong class="slate-bold">IMPORTANT NOTE ON ERROR HANDLING:</strong>
This API uses a non-standard error handling pattern in its /v1 endpoints, where most errors return HTTP 500 status code
regardless of the error type. The actual error type is indicated by the <code class="slate-code">errors</code> field in the response. Check the ApiError schema for the list of error strings.
Exceptions to this pattern are explicitly noted in individual endpoint descriptions.</p><h2 class="slate-h2 " >Authentication</h2><p class="slate-p " >This API uses two primary authentication methods:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Key - </strong>All calls must be made with your Fusion API Key in the X-API-KEY header</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">JWT Token - </strong>All calls specific to a user e.g. checkout sessions and subscriptions must also contain a valid JWT token in the Authorization header in the format ‘Bearer TOKEN’. This token must contain the ‘sub’ claim which serves as the unique ID for the customer across the Fusion system. </div></li></ul><p class="slate-p " ></p><p class="slate-p " ></p>

Fusion API Reference

<p class="slate-p " >These endpoints allow you to return Stripe products and prices to display to your users so that they can purchase them. They are all accessible using your Fusion API key and do not require a JWT token from the user. </p><p class="slate-p " ></p>

Product

<p class="slate-p " >These endpoints allow you to perform monetization operations, and proxy through the Stripe, a world leading payment platform that is the technology underpinning of Fusion monetization. Here you will find endpoints for creating checkout sessions, retrieving checkout information and giving access to the customer portal.</p><p class="slate-p " ></p>

Billing

<p class="slate-p " >These endpoints are for the checking of customer entitlements, establishing what a customer has access to and what products they should be able to purchase.</p><p class="slate-p " ></p>

Subscriptions

Preferences

Default

Fusion

Production server

Staging server

Local development server

Check User Subscription

Create Checkout Session

Create Customer Portal Link

Get Active Subscriptions for a User

Get current user's preferences

Get preference schema

Get Price by ID

Get Product by ID

List Products

Retrieve Stripe Checkout Session by ID

Update current user's preferences

<p class="slate-p " >API for managing monetization operations and proxying Stripe calls.</p><h2 class="slate-h2 " >Authentication</h2><p class="slate-p " >This API uses two primary authentication methods:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">API Key - </strong>All calls must be made with your Fusion API Key in the X-API-KEY header</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">JWT Token - </strong>All calls specific to a user e.g. checkout sessions and subscriptions must also contain a valid JWT token in the Authorization header in the format ‘Bearer TOKEN’. This token must contain the ‘sub’ claim which serves as the unique ID for the customer across the Fusion system. </div></li></ul><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

API for managing monetization operations and proxying Stripe calls.

This API uses two primary authentication methods:

Sections