issues

Merges one or more issues into a primary issue. All issues must belong to the same account (or, without an account, the same requester). All issues are found and validated before anything changes, so a request rejected for a missing or ineligible issue merges nothing. Closing messages are sent before the merge and are not recalled: if sending one fails, or the merge fails afterwards, duplicates processed earlier may already have received it. This cannot be undone.

Rate limit: 30 requests per minute

post/issues/merge

Request

  • Base URL
    https://api.usepylon.com
  • URL
    https://api.usepylon.com/issues/merge
  • Auth
    HTTP bearer

Request body

closing_messagestring

Optional plain-text message sent to the customer on each merged Slack or form issue before it is merged.

duplicate_issue_idsstring[] required

The IDs or numbers of the issues to merge into the primary issue. Must contain between 1 and 50 issues, all in the same account as the primary issue.

primary_issue_idstring required

The ID or number of the issue to merge into. It keeps its ID and receives the messages of the merged issues.

Response

request_idstring required

The request ID for tracking.

Example response

{
  "data": {
    "business_hours_time_in_status_seconds": {
      "new": 120,
      "waiting_on_customer": 1800
    },
    "custom_fields": {
      "priority": {
        "value": "high"
      }
    },
    "state": "new",
    "time_in_status_seconds": {
      "new": 120,
      "waiting_on_customer": 3600
    },
    "workspace_phone_number": "+14155551234"
  }
}

Changes

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property / to the response with the status