Custom API Integration

Use a custom API or SDK integration when personalization depends on runtime data from your own systems, such as authenticated user state, product usage, CDP enrichment, account data, recommendations, pricing, eligibility, or backend decisioning.

This path gives the implementation team full control over what data is fetched, transformed, and passed into the MP5 player.

Start in Platform Integration to collect the project-specific SDK and field details:

Integration

Use Simulation separately when you need to preview backend states before connecting the API.

Simulation

When to Use a Custom API

• Personalization should use secure backend logic.

• Data should not appear in the URL.

• Multiple internal systems need to be combined before render.

• The MP5 is embedded in an authenticated website, product, portal, or app.

• The experience needs live context such as account status, product state, availability, location, device state, or eligibility.

• The implementation team wants to own hosting, routing, analytics wrappers, consent controls, or page behavior.

Custom API data passed into the Blings SDK.

Implementation Flow

1

Confirm the MP5 Field Schema

In Platform, open Settings -> Dynamic Data and record the exact field names, expected value types, and required fields.

2

Simulate the Important States

Create Simulation profiles that match the backend states your API will return, such as eligible, ineligible, premium, expired, missing image, or alternate offer.

3

Copy SDK Details from Platform

Open Integration and copy the project-specific SDK or custom code instructions. Confirm the project ID, selected lineup or scene path, and any player settings required by the project.

4

Fetch or Assemble Data

Use your application or backend to fetch the viewer data, normalize it to the MP5 field schema, and apply fallback logic before initializing the player.

5

Pass Data into the Player

Initialize the Blings player with the JSON payload and test it against the same values used in Simulation.

Example

fetch("https://my-api.example.com/user-data/123")
  .then((response) => response.json())
  .then((userData) => {
    BlingsPlayer.create({
      project: {
        id: "project-id-from-platform"
      },
      settings: {
        container: document.getElementById("blings-video-container")
      },
      data: userData
    });
  });

The userData keys must match the field names in the Blings project schema.

{
  "first_name": "Jordan",
  "plan": "Premium",
  "recommended_offer": "travel-upgrade",
  "profile_image": "https://example.com/jordan.jpg"
}

QA Checklist

• The API response maps exactly to the Dynamic Data field names.

• Sensitive values are handled according to the customer's privacy and security requirements.

• Missing values return defaults that the MP5 can render safely.

• Image, audio, and video URLs are accessible from the viewer's device.

• The page is tested with the same states used in Platform Simulation.

• Analytics and event handling are tested in the hosting page or app.

Related Guides

Getting Started with Blings.io Dynamic Video SDKEmbedding Blings MP5 Videos in Mobile Apps