Choose the correct environment
DVM separates Sandbox and production. Use credentials and endpoints for the same environment throughout a request flow.
Other API families can use endpoints documented for that API or supplied during onboarding.
Authenticate API requests
Using OAuth 2.0 Client Credentials is the default and recommended authentication method for enterprise DVM integrations. Request an access token for the relevant environment, cache it, and send it in supported API requests:Follow the API contract
Use the current API reference for operation paths, request and response fields, headers, status behavior, and authentication supported by each API. Request identifiers, idempotency behavior, and retry handling can vary by API and integration. Where an operation defines these behaviors, follow that API contract rather than applying a common rule across all DVM APIs. Treat versioned paths and immutable technical identifiers exactly as published. Do not infer current behavior from legacy Bango API documentation. Use the API changelog to review published changes across the DVM APIs.Test in Sandbox
Validate your integration in Sandbox before production. Use the Testing overview for the DVM testing path and certification stages. For Reseller-to-DVM Entitlement API testing, you can use mock response headers to simulate defined Content Provider responses.X-Magic-Number is specific to that Entitlement API testing flow and is not a general DVM API header.
Before production
Confirm that your integration:- Uses production credentials and production endpoints.
- Caches and refreshes OAuth2 access tokens correctly where OAuth2 is configured.
- Follows the request headers and retry behavior documented for each API operation.
- Processes the notifications required for the integration.
- Has completed the testing and certification agreed with Bango.

