Get App Info
After the OAuth authorization is successful, Cisco DNA Spaces retrieves the App information from the partner site by calling the appInfo API request and passing the access token value that was retrieved, earlier.
Method: GET
Note | Note: The App Info URL is configured on the Partner App > App Tile section. Make sure to use the HTTPS protocol. |
API Endpoint: <$App Info URL>
Path: appInfo
Content-Type: application/json
Authorization: Bearer <access_token>
access_token: <JWT-token>
For example:
eyJlbWFpbCI6InN1cmVuZHJuQGNpc2NvLmNvbSIsImN1c3RvbWVyIjoiVHJpZ3VlIiwidmVyIjoi
djEiLCJ1aWQiOiJDOEFCNTU0RDZGODA0QjhFQjYyNDZENDREM0RFNEI0NiIsImlhdCI6MTU1MzU5MjE5OSwib
3JpZ2luYWxfaWF0IjoxNTUzNTkyMTk5LCJleHAiOjE1NTM1OTgxOTl9.CMB8AVaAybKM5aMSXc9K-HVpf8Yh
I_uyfMelXVFyZu002LK_ph17xAnPRtYQPTam_P61g2pkfWNvvvmeQSYPbA
Note | The access_token:<JWT-token> is a part of the Get Access token API response. |
Query-Params: partnerTenantId: <Customer account ID maintained by the Partner>
Data Parameter | Description | Allowed values |
---|---|---|
Bearer: access_token | The Bearer token is the JWT generated and signed by the Cisco DNA Spaces Server, which can be validated with the Public Certificate downloaded from the Cisco DNA Spaces – Partner Dashboard. | String |
partnerTenantId | The accountId parameter is the Customer’s unique Identifier maintained by the Partner. | String |
Response Format:
{
"telemetry": [
{
"type": "number",
"name": "Feedback",
"value": "7",
"units": "instance of feedback"
},
{
"type": "number",
"name": "Engagements",
"value": "6",
"units": "Engagements"
},
],
"partnerTenantId": "<partnerTenantID>",
"userEmail": "johndoe@cisco.com",
"supportEmail": "support@<partner-name>.com"
}
Note:
The supportEmail parameter is an optional.
The userEmail parameter can be extracted from the JWT token.