The client application must be registered with the Hybrid Data Pipeline server. When you register the client application with Hybrid Data Pipeline, a client ID and client secret are returned. The client ID and client secret are required for the client application to obtain access and refresh tokens. You may register the client application with the OAuth client authorization API.

Prerequisites

Before you send the required POST request, you must have the Client application Redirect URL. The Redirect URL is the client application endpoint which a user is redirected to after authorization. Multiple Redirect URLs may be provided. If you plan to test a grant flow using Postman, you would specify Postman's Callback URL: 
https://www.getpostman.com/oauth2/callback

The registration request

The registration request is a POST request with a payload that includes a name, a description, and the Redirect URL(s). The following example registers Postman as a client application.

POST https://MyServer:8443/api/mgmt/oauth/client/applications

{
    "name":"Postman",
    "description":"Testing authorization code flow",
    "redirectUrls":[
       "https://www.getpostman.com/oauth2/callback"
       ]
}

With a successful request, a response payload with a client ID and client secret will be returned. For example:

{
    "id":"19",
    "name":"Postman",
    "description":"Testing authorization code flow",
    "redirectUrls":[
       "https://www.getpostman.com/oauth2/callback"
    "clientId":"315368974.apps.hdptest.com",
    "clientSecret":"96dab351-cd80-4dfc-8756-8afe9896e92f"
       ]
}

For further details about registering and managing client applications, see OAuth client authorization API