Skip to main content
POST
/
schedule
/
self
List my schedules
curl --request POST \
  --url 'https://api.flashcat.cloud/schedule/self?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "start": 1712000000,
  "end": 1712086400
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "items": [
      {
        "id": 2539108069860,
        "name": "Open Source Q&A",
        "account_id": 2451002751131,
        "group_id": 2477033058131,
        "disabled": 0,
        "create_at": 1702623874,
        "create_by": 2451002751131,
        "update_at": 1710468081,
        "update_by": 2476444212131,
        "layers": [
          {
            "account_id": 2451002751131,
            "name": "Rule 1",
            "schedule_id": 2539108069860,
            "hidden": 0,
            "mode": 0,
            "weight": 0,
            "groups": [
              {
                "group_name": "A",
                "name": "A",
                "members": [
                  {
                    "role_id": 0,
                    "person_ids": [
                      2476444212131
                    ]
                  }
                ],
                "start": 0,
                "end": 0
              },
              {
                "group_name": "B",
                "name": "B",
                "members": [
                  {
                    "role_id": 0,
                    "person_ids": [
                      2469167612131
                    ]
                  }
                ],
                "start": 0,
                "end": 0
              }
            ],
            "rotation_duration": 86400,
            "handoff_time": 0,
            "enable_time": 1702623874,
            "expire_time": 0,
            "restrict_mode": 0,
            "restrict_start": 0,
            "restrict_end": 0,
            "restrict_periods": [],
            "day_mask": {
              "repeat": [
                1,
                2,
                3,
                4,
                5
              ]
            },
            "create_at": 1702623874,
            "create_by": 2451002751131,
            "update_at": 1710468081,
            "update_by": 2476444212131,
            "layer_name": "Rule 1",
            "fair_rotation": false,
            "layer_start": 1702623874,
            "layer_end": null,
            "rotation_unit": "day",
            "rotation_value": 1,
            "mask_continuous_enabled": false
          }
        ],
        "schedule_layers": null,
        "final_schedule": {
          "layer_name": "",
          "name": "",
          "mode": 0,
          "schedules": null
        },
        "notify": {
          "fixed_time": null,
          "by": null,
          "webhooks": null
        },
        "schedule_id": 2539108069860,
        "schedule_name": "Open Source Q&A",
        "team_id": 2477033058131,
        "description": "",
        "layer_schedules": null,
        "status": 0,
        "cur_oncall": null,
        "next_oncall": null
      }
    ]
  }
}

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
PermissionsSchedules Read (on-call) or Schedules Manage (on-call)

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

Query parameters for listing the current user's schedules. Both start and end are Unix timestamps (seconds). If omitted they default to 0. The window must not exceed 30 days.

​
start
integer<int64>

Window start (Unix seconds, 10 digits).

​
end
integer<int64>

Window end (Unix seconds, 10 digits). Must be within 30 days of start.

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

Response of /schedule/self and /schedule/infos. Only the items field is populated.