Get ServiceDeskPlus linked incidents
List synchronization mappings between ServiceDeskPlus requests and Flashduty incidents.
Restrictions
Usage
- Use this endpoint to inspect synchronization mappings between ServiceDeskPlus requests and Flashduty incidents, including the external request link and sync status.
- When
incident_idis not provided,start_timeandend_timeare required Unix-second timestamps; the time window cannot exceed 30 days. statusaccepts onlysuccessandfailed, representing successful and failed synchronization records.- Results are sorted by the internal record ID. Set
asctotruefor ascending order; otherwise records are returned descending. Pass the returnedsearch_after_ctxto continue pagination.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Filters for listing ServiceDeskPlus request synchronization records. A time window is optional when querying by incident ID; otherwise provide a Unix-second window no longer than 30 days.
Window start, Unix seconds. Optional when incident_id is provided.
x >= 0Window end, Unix seconds. Must be greater than or equal to start_time. Optional when incident_id is provided.
x >= 0Synchronization status filter.
success, failed Channel IDs to filter by.
ServiceDeskPlus integration ID.
x >= 0Flashduty incident ID. When set, the time window can be omitted.
64ServiceDeskPlus request ID.
64When true, sort by internal record ID ascending; otherwise descending.
Page number starting at 1. Ignored when search_after_ctx is set.
x >= 0Page size. Defaults to 20; maximum 100.
0 <= x <= 100Cursor returned by the previous page.
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.