Skip to main content
POST
Get ServiceDeskPlus linked 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_id is not provided, start_time and end_time are required Unix-second timestamps; the time window cannot exceed 30 days.
  • status accepts only success and failed, representing successful and failed synchronization records.
  • Results are sorted by the internal record ID. Set asc to true for ascending order; otherwise records are returned descending. Pass the returned search_after_ctx to continue pagination.

Authorizations

app_key
string
query
required

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

application/json

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.

start_time
integer<int64>

Window start, Unix seconds. Optional when incident_id is provided.

Required range: x >= 0
end_time
integer<int64>

Window end, Unix seconds. Must be greater than or equal to start_time. Optional when incident_id is provided.

Required range: x >= 0
status
enum<string>

Synchronization status filter.

Available options:
success,
failed
channel_ids
integer<int64>[]

Channel IDs to filter by.

integration_id
integer<int64>

ServiceDeskPlus integration ID.

Required range: x >= 0
incident_id
string

Flashduty incident ID. When set, the time window can be omitted.

Maximum string length: 64
request_id
string

ServiceDeskPlus request ID.

Maximum string length: 64
asc
boolean

When true, sort by internal record ID ascending; otherwise descending.

p
integer<int64>

Page number starting at 1. Ignored when search_after_ctx is set.

Required range: x >= 0
limit
integer<int64>
default:20

Page size. Defaults to 20; maximum 100.

Required range: 0 <= x <= 100
search_after_ctx
string

Cursor 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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Paginated list of ServiceDeskPlus request synchronization records.