Skip to content

Deduplication

Tired of duplicate tickets? Then use the available deduplication methods.

Dedup key

For channels with API integrations, if multiple tickets are created for the same issue, your team will be notified of each (duplicate) ticket. To group these tickets, you will want to include the parameter dedupKey in your request body when creating tickets.

DutyCalls de-duplicates incidents based on the dedupKey parameter. If there are no open (unresolved) tickets with this key, a new ticket will be created. If there is already an open ticket with a matching key, this event will be appended to that ticket as a hit.

Example

An example of using the dedupKey can be found below.

curl -X POST "https://dutycalls.me/api/ticket?channel=$CHANNEL_NAME"
    -H  "accept: application/json"
        -H  "Content-Type: application/json"
            -H "Authorization: Basic $CREDENTIALS"
                -d {
                        "title": "This is the title of the ticket",
                        "body": "This is the body of the ticket",
                        "severity": "medium",
                        "dedupKey": "$MY_UNIQUE_KEY"
                    }

Hit API

It is also possible to use the API endpoint made specifically for adding hits to tickets. Checkout the specifications of this endpoint in Swagger.

Example

In addition to the credentials and the data itself, the sid or sids of the targeted tickets must also be included in the HTTP request. These must be added as the value of the query parameter sid in the URI of the request. An example of this can be seen below.

curl -X POST "https://dutycalls.me/api/ticket/hit?sid=$TICKET_SID"
    -H  "accept: application/json"
        -H  "Content-Type: application/json"
            -H "Authorization: Basic $CREDENTIALS"
                -d {
                        "summary": "This is the summary of the ticket hit",
                        "timestamp": 1637764283043,
                        "ticketProperties": {
                            "severity": "medium",
                            "links": [
                                "https://my-domain.com"
                            ]
                        }
                    }