Skip to main content
Media you can view may include a playback descriptor. Pass it to a DRM-capable player. OFAuth handles authorization for the linked account. Start with Play DRM video, or Retain DRM video in Vault+.

Supported playback

Dynamic DASH manifests, segment templates, external resource references, and multiple alternative base URLs are rejected. A successful manifest or license response alone does not establish browser compatibility. The browser must decode frames and play audio.

Playback descriptor

For Access responses, playback belongs to the media item. For Vault+ responses, it belongs to the retained variant in the item’s media map.
The URLs above illustrate the shape. Use the complete URLs returned by the API. playback is optional. It is returned for supported protected media the linked account can view. Media marked canView: false receives no descriptor. A missing descriptor is not permission to construct a license URL or play a protected manifest as an ordinary file.

Authentication and delivery

Access and Vault+ API calls use the External OAuth bearer token and x-linked-account-id. Requests to the returned media URLs use the signed URL itself. The player does not need an API bearer token, OnlyFans cookies, signing rules, or custom origin headers. Each request rechecks current authority. A signed URL does not preserve access after revocation. Keep these URLs out of analytics and logs, and pass them only to the authorized viewer. The player uses the returned URLs for media and license requests. Keep the linked account connected and its access active during playback.

Expiry and renewal

Manifest, resource, and license URLs last at most 30 minutes. Configuration can shorten this period, and live CDN credentials can expire sooner. expiresAt is the value your integration uses. The renewal URL lasts 24 hours from descriptor issuance. Renewal returns a complete new descriptor, including a new renewal URL. After that URL expires, obtain the media again through Access or Vault+. Renewal checks current access and returns fresh playback URLs. If renewal fails, fetch a new media response through Access or Vault+.

Playback failures

Media-proxy failures can be plain text. They do not use the Access API JSON error envelope. Check the HTTP status before parsing a renewal response as JSON. When you report a failure, include the failing stage, HTTP status, response text, browser, and player error code. Include the parent API request’s x-request-id. Exclude signed URLs and binary license bodies from shared diagnostics.