Get registered application by ID
- Last Updated: March 6, 2025
- 1 minute read
- Hybrid Data Pipeline
- Version 4.6
- Documentation
Purpose
Returns registered application by ID.
URL
https://<myserver>:<port>/api/mgmt/oauth/client/applications/{id}
Method
GET
URL Parameters
<myserver> is the hostname or IP address of the machine hosting the Hybrid Data Pipeline server for a non-load balancer deployment, or the machine hosting the load balancer for a load balancer deployment. For a non-load balancer deployment, <port> is the port number specified as the Server Access Port during deployment. For a load balancer deployment, <port> must be either 80 for http or 443 for https. Whenever port 80 or 443 are used, it is not necessary to include the port number in the URL.
| Parameter | Description | Valid Values |
|---|---|---|
| "id" | The application ID is automatically generated with the successful registration of the application. | It must be a valid application ID. |
Response Definition
The response takes the following format. The parameters of the response are described in the table that follows.
{
"id":"app_id,
"name": "app_name"
"description":"app_description",
"redirectUrls": [
"redirect_url1","redirect_url2",...
],
"clientId": "string",
"clientSecret": "string"
}
| Property | Description | Valid Values |
|---|---|---|
| "id" | The application ID is automatically generated with the successful registration of the application. This ID is used for tracking applications in Hybrid Data Pipeline. | An auto-generated application ID. |
| "name" | The name of the application | A string with a maximum length of 128 characters. |
| "description" | User specified description of the application. | A string with a maximum length of 256 characters. |
| "redirectUrls" | List of authorized URLs | This may be one valid URL or a comma separated list of valid URLs. |
| "clientId" | The client ID is generated when the client application is registered. This ID is required when client applications initiate OAuth authorization. | An auto-generated value used when client applications initiate OAuth authorization. |
| "clientSecret" | The client secret is generated when the client application is registered. This secret is required when client applications initiate OAuth authorization. | An auto-generated value used when client applications initiate OAuth authorization. |
Sample Server Success Response
Status code: 200
Successful response
{
"id":19,
"name":"Application1",
"description":"Application1 for Create with all Fields",
"redirectUrls":["bedford.progresstest.com","americas.progresstest.com"],
"clientId":"315368974.apps.hdptest.com",
"clientSecret":"96dab351-cd80-4dfc-8756-8afe9896e92f"
}
Sample Server Failure Response
{
"error":{
"code":222206630,
"message":{
"lang":"en-US",
"value":"There is no OAuth Client Application with that id:{id}.."
}
}
}
Authentication
Basic Authentication using Login ID and Password
Authorization
Any active Hybrid Data Pipeline user