Skip to main content
GET
/
status-page
/
subscriber
/
list
List status page subscribers
curl --request GET \
  --url 'https://api.flashcat.cloud/status-page/subscriber/list?app_key='
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "total": 2,
    "has_next_page": false,
    "items": [
      {
        "recipient": "alice@example.com",
        "method": "email",
        "components": [],
        "all": true,
        "locale": "zh-CN"
      },
      {
        "recipient": "bob@example.com",
        "method": "email",
        "components": [],
        "all": true,
        "locale": "en-US"
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsNone — any valid app_key can call this operation

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.

Query Parameters

page_id
integer<int64>
required

Status page ID.

component_ids
string

Comma-separated component IDs to filter subscribers by.

p
integer<int64>
default:1

Page number (1-based).

Required range: x >= 1
limit
integer<int64>
default:10

Page size (1-100).

Required range: 1 <= x <= 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
required

Paginated list of status page subscribers.