Skip to main content
POST
List alerts by IDs

Restrictions

Usage

  • A malformed ID fails the request with InvalidParameter; well-formed IDs not found in the account are left out of items.
  • The response is not paginated: total is always 0, has_next_page is always false, and search_after_ctx is omitted.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json
alert_ids
string[]
required

Alert IDs (ObjectID hex strings) to fetch. A malformed ID fails the request; IDs not found in the account are left out of the result. At most 100 items per request; split larger sets into several calls.

Maximum array length: 100

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

Paginated list of alerts.