Integrating OpManager with TOPdesk enables seamless incident management by automatically logging network alerts as incidents in TOPdesk. This guide walks you through the integration steps to create, update, close, and reopen incidents from OpManager into TOPdesk using APIs.
OpManager can be integrated with TOPdesk using the custom integration option.
Steps to perform in OpManager
Method: POST
API Endpoint: https://<Instance base URL>/tas/api/incidents
Payload Type: JSON
Data Type: Raw
Request Body:
{
"briefDescription": "$stringseverity - $displayName",
"request": "alert: $message",
"action": "Category: $category - $displayName - $strModTime",
"status": "secondLine",
"callerLookup": {
"networkLoginName": "<User_Name>"
},
"category": {
"id": "c8322xacsaxx87877aaszaxsa908c"
},
"subcategory": {
"id": "7f9436c6dsafcdws8i878swqw25"
},
"processingStatus": {
"id": "325o908dfcsdfdcsd0114ebf7e891"
}
} Note: Replace <User_Name> with the TOPdesk login username and <Instance base URL> with instance ID. Ensure a valid processingStatus.id is provided to define the incident's initial status. Payload varies based on user requirements. Refer to category, sub-category, and processing status to get the corresponding IDs used in the incident payload.

Click "Test Action" to verify the request. Once successful, click "Manage Incident" to retrieve the unique value from the response (e.g., the incident number). This unique identifier is used to manage the specific incident.

Method: POST
API Endpoint: https://<Instance base URL>/tas/api/incidents/number/$.number
Payload Type: JSON
Data Type: Raw
Request Body:
{
"briefDescription": "$stringseverity - $displayName",
"request": "alert: $message",
"action": "Category: $category - $displayName - $strModTime",
"status": "secondLine",
"callerLookup": {
"networkLoginName": "<User_Name>"
},
"category": {
"id": "c8322080-94f2-4680-9b4d-527f7d2e7cac"
},
"subcategory": {
"id": "7f9436c6-98c6-4c7scscr4-9d-d0a9ae3f9055"
},
"processingStatus": {
"id": "325ded26-refe55657-tgr54c3-0114ebf7e891"
}
} Note: Replace <User_Name> with the actual TOPdesk login username and <Instance base URL> with instance ID. The request body should match the creation payload, but with an updated processingStatus.id to reflect a new status (e.g., “In Progress”, “Assigned”). This transitions the incident to the appropriate workflow state. Payload varies based on user requirements. Refer to category, sub-category, and processing status to get the corresponding IDs used in the incident payload.

Closing an incident uses the same POST method and URL format as updating. The key change is setting processingStatus.id to a value that maps to a "Closed" or "Resolved" status in your TOPdesk system. This action marks the incident as resolved and completes the tracking lifecycle in the helpdesk.
Method: POST
API Endpoint: https://<Instance base URL>/tas/api/incidents/number/$.number
Payload Type: JSON
Data Type: Raw
Request Body:
{
"briefDescription": "$stringseverity - $displayName",
"request": "alert: $message",
"action": "Category: $category - $displayName - $strModTime",
"status": "secondLine",
"callerLookup": {
"networkLoginName": "<User_Name>"
},
"category": {
"id": "c8322xacsaxx87877aaszaxsa908c"
},
"subcategory": {
"id": "7f9436c6dsafcdws8i878swqw25"
},
"processingStatus": {
"id": "325o908dfcsdfdcsd0114ebf7e891"
}
} Note: Replace <User_Name> with your TOPdesk login user name and <Instance base URL> with instance ID. Payload varies based on user requirements. Refer to category, sub-category, and processing status to get the corresponding IDs used in the incident payload.

To reopen a closed incident, send a POST request to the same incident URL. The request must contain a processingStatus.id corresponding to an “Open” or “In Progress” status. This allows the incident to be reopened and further actions to be taken.
Note that this is only applicable for reopening an incident. This is not applicable if you Create a new incident.
Method: POST
API Endpoint: https://<Instance base URL>/tas/api/incidents/number/$.number
Payload Type: JSON
Data Type: Raw
Request Body:
{
"briefDescription": "$stringseverity - $displayName",
"request": "alert: $message",
"action": "Category: $category - $displayName - $strModTime",
"status": "secondLine",
"callerLookup": {
"networkLoginName": "<User_Name>"
},
"category": {
"id": "c83225fdfre-94f2-4911-9b4d-527f7d2e7cac"
},
"subcategory": {
"id": "7f9436c45775-8c6-4c71-af9d-d0a9ae3f9055"
},
"processingStatus": {
"id": "325ded26-849e-4c954354-4c6-0114ebf7e891"
}
} Note: Replace <User_Name> with your TOPdesk login user name and <Instance base URL> with instance ID. Payload varies based on user requirements. Refer to category, sub-category, and processing status to get the corresponding IDs used in the incident payload.


Refer to the steps below to configure multiple notification profiles.
Follow the steps below to configure the notification profile:

Trigger a real-time alert in OpManager. Then, log in to your TOPdesk interface to verify the alert has been logged as an incident.
Know more about the integrations offered by OpManager
Know more about dynamic variables used in request body
Thank you for your feedback!