Security and Authorization V2


This documentation describes how to use the platform's standard security API to request an access token that can be used to access other APIs on the platform. The downloadable OpenAPI specification above reflects this implementation. This version of the API is fully compliant with the conventions defined in the OAuth 2.0 specification.


Consumers should note that the token name usage this version onward is, access_token. The previous API v1 token name usage was accessToken.

Certain legacy APIs exposed through this platform, use a legacy Authorization implementation described at the bottom of this summary. Review the Change Log/Release Notes to determine whether a given API uses the standard or legacy Authorization mechanism.

Access Control through Web Tokens

All Change Healthcare Enterprise APIs on this platform are secured using JSON Web Tokens (JWT).

Security and Authorization

Security through TLS

All calls to Change Healthcare APIs are encrypted over HTTPS. Our APIs support connections using Transport Layer Security (TLS) version 1.2 or later.

Bearer token through OAuth2

The Change Healthcare uses OAuth2 to create a secure connection with our API users, which requires a bearer authorization token to obtain access.



The lifespan of a Bearer token is one hour (3600 seconds) for both sandbox and production environments.

We recommend automating transactions to use the tokens generated over the token lifespan. Obtaining tokens for each transaction is less efficient and does not improve the security criteria for any transactions.

APIs components

API ComponentsValue
Bearer Authorization Token Endpoint/apip/auth/v2/token
Request MethodPOST
Content-Type HeaderAlways defaults to application/json
Authorization HeaderPass the Bearer authorization token to authorization header
grant_type FieldAlways client_credentials

Generate API bearer token

Bearer token request header

Content-Type: application/json
Authorization: Bearer <Your-Access-Token>

Bearer token request

curl -X POST \
  '****' \
  -H 'Content-Type: application/json' \
  -d '{
  "client_id": "<Your-ClientId>",
  "client_secret": "<Your-ClientSecret>",
  "grant_type": "client_credentials"

Bearer token request example

curl -X POST \ \\
    -H 'Content-Type: application/x-www-form-urlencoded' \\
    -d 'client_id=hghjhgjtgjtgjhhhjasdfhghjhgj\&client_secret=asdfdfjsdhfjhsdhf\&grant_type=client_credentials'

Bearer token request body

When you use an API client, such as a Postman tool, the JSON body for the request
must appear as follows:

    "client_id": "hghjhgjtgjtgjhhhjasdfhghjhgj",
    "client_secret": "asdfdfjsdhfjhsdhf",
    "grant_type": "client_credentials"

Bearer token response

To test on your sandbox, use your client_id and client_secret to get your token. If you do not have your credentials, reach out to your account manager or contact in Change Healthcare.


    "token_type": "bearer",
    "expires_in": 3600



When you are ready to move from sandbox to production, replace the sandbox authorization URL with the production URL:

Production API credentials

You will need a separate set of credentials for the production APIs. For more information, see API Onboarding.

You can use your bearer token to call all your contracted Change Healthcare APIs with these HTTP headers:

  • Content-Type: application/json
  • Authorization: Bearer

Legacy Authorization

For more information about the legacy Authorization APIs implementation: