Get Started
How it works
Each partner picks the integration path that fits its team and use case. Here's how the two compare and what the lifecycle looks like for each.
API vs Iframe at a glance
| API Integration | Iframe Integration | |
|---|---|---|
| Backend required | Yes | No |
| Who takes payment | Partner, then notifies Osteocom | Osteocom, directly |
| UI control | Full — you build the storefront | Branded card, themeable |
| Time to integrate | Days to weeks | Minutes |
| Maintenance | Partner maintains the flow | Effectively zero |
API integration lifecycle
Authenticate, read the catalog, authorize a customer after purchase, then render the video with an issued token.
Phase 1
Authenticate
access token
Phase 2
Read catalog
channels + videos
Phase 3
Authorize
after purchase
Phase 4
Render video
issued token
For the step-by-step calls see the Quickstart; every field is documented in the API Reference.
Iframe integration lifecycle
Shorter, because Osteocom hosts the storefront card and runs the checkout. You only embed the iframe and pass a stable user id.
1
Embed iframe
on your page
2
Customer buys
on Osteocom
3
Activation
automatic
4
Already owned
on next load
The full walkthrough lives in Iframe Integration.