Skip to main content
DVM uses different authentication paths for people using DVM applications and systems integrating with DVM APIs.

User authentication

Single sign-on (SSO) authenticates people who access DVM. After authentication, access is determined by the Partner, environment, and user role assigned to the user. To set up SSO, contact support@bango.com. See Manage users and roles for how access and permissions are controlled.

API authentication

API credentials authenticate machine-to-machine integrations. They are separate from the SSO credentials used by people signing in to DVM. Bango provisions OAuth 2.0 client credentials for your integration during onboarding and technical setup. Use the credentials and token endpoint configured for your environment. Sandbox and Production use separate credentials. The OAuth 2.0 Client Credentials grant is the default and recommended authentication method for enterprise DVM integrations. Some existing integrations use Basic authentication where this has been configured. Authentication support is specific to the API and integration. Authentication allows your systems to call the APIs they are authorized to use; it does not establish a Partnership or create a Route. Where technical configuration depends on region and environment, it relates to the relevant Regional Entity rather than human Partner access. See Regional Entities. Follow OAuth 2.0 authentication for the complete token request, response, caching, Bearer header, and error handling guidance. See Working with DVM APIs for API environment and testing conventions. Use the authentication method documented for the API and configured during onboarding.