Create server integration credentials

Find your Environment ID, Site Key, Access Key, and Content ID. Keep credentials on your trusted backend.

View Markdown Live examplesUpdated 2026-10-21

Create these credentials after your Published content plays in the DRM-X Web Player. They allow your backend to request playback for an authorized viewer. They do not replace your website login or packaging profile.

Create the playback API client#

Choose the environment.Sign in to DRM-X Console and select the Development environment that contains your Published content.
Create a client.Open Integrations and create a Playback API client for your website backend. Grant only license-tokens:create.
Copy the server values.Keep the Site ID, Site Key and one-time Access Key in protected server configuration. The Site ID identifies the environment. Copy the Content ID from its Published protected file.
Configure and test the sample.Use the kit for your backend. Replace the placeholders below and the example login and entitlement check. Confirm that an entitled viewer can play and a viewer without access is denied.

Account setup

Copy the four values used by the quick start#

Create a playback API client in Console → Integrations and grant only license-tokens:create. Get the Content ID from the Published protected file created in Console → Package content.

Find your integration values

Copy these values from DRM-X Console. Keep credentials on your server.

Environment ID / Site ID
Select the environment that contains your published video.
Site Key / Client ID
Copy the identifier of your playback API client.
Access Key
Save this secret when it is first shown. Do not send it to the browser.
Content ID
Copy the Content ID of a video whose status is Published.

Access Keys must remain server-side.

PHP code-first settings

return [
    'platformApi' => 'https://api6.drm-x.com',
    'siteId' => 'your-development-environment-uuid',
    'siteKey' => 'drmx_your_environment_scoped_client_id',
    'accessKey' => 'paste-your-one-time-access-key',
    'applicationId' => 'customer-php-website',
    'content' => [
        'id' => 'your-published-content-id',
        'title' => 'Your protected title',
        'type' => 'vod',
    ],
    'licensePolicyTemplate' => 'multi-tier-standard',
    'licensePolicy' => null,
    'licenseDeliveryMode' => 'direct-token',
];

No environment variables are required for the downloaded quick start. The example contains commented production alternatives for environment or secret-manager injection.

Never ship these valuesDo not place the Site Key or Access Key in HTML, JavaScript, an APK, an IPA, application resources, mobile CI variables, URLs, logs, analytics, or downloadable configuration.

Use a different API client for each application or backend service so one credential can be rotated or revoked without interrupting every integration.

Keep packaging and playback credentials separate#

Purpose	Values	Where to use them
Package and publish	Site ID, Packager Access Key, Packager KMS Token	Packager saved profile or protected automation environment
Authorize a viewer	Site ID, Site Key, Access Key	Your authenticated backend only
Play one authorized item	Short-lived DRM License Token and Contract v1	Player, using the returned bounded routes

A Packager KMS Token cannot replace a playback Access Key. A viewer DRM License Token cannot publish content. Use Development credentials for integration, then separate Production credentials. Rotate or revoke exposed secrets and update the affected application.

First verify the Published Content ID in the signed-in Web Player. Then configure the same environment and trusted Content ID in your backend kit.