Shopify protected video

Configure the custom app#

Configure a Shopify app proxy that forwards a storefront path to /shopify/proxy on the HTTPS Node bridge. Store the app secret, myshopify.com store name and Admin API access token only in the server configuration. Request the customer and order read scopes needed by your store.

Create a bridge resource with provider=shopify and externalResource set to the numeric Shopify product ID. Its Content ID and license policy remain server-owned. Link the storefront customer to the proxy path with the internal resource name.

Download third-party integration source

Verify the customer and purchase#

The bridge validates the app-proxy HMAC, timestamp, store and signed logged_in_customer_id. Anonymous requests are denied. It then queries the matching customer’s orders through the Admin GraphQL API and requires a paid, uncancelled order with a remaining quantity of the mapped product.

The proxy returns a link with a one-use, 30-second ticket. Opening it displays the player on the bridge origin, where the session API can remain same-origin. Each new playback request rechecks the purchase.

Store-specific validation#

This preview targets customer identities supplied by the signed app proxy. New customer-account extensions, subscription renewals, bundles and third-party membership apps need separate adapters; do not assume that a storefront Liquid customer variable authorizes playback.

The order scan is bounded to 20 pages of 50 orders and the first 100 line items in each order. Shopify may restrict historical orders unless the app has approved all-orders access. Requests outside this coverage are denied; use a verified entitlement ledger for larger stores or long-lived purchase access.

Local signature and authorization tests are available. A development store must still test login, paid and refunded orders, canceled orders, old purchases, altered product IDs and real DRM playback before release.

Shopify app-proxy authentication