Skip to main content
POST
Batch get schedules

Restrictions

Usage

  • Returns stored configuration only: layers, schedule_layers, layer_schedules, cur_oncall and next_oncall are always null, and final_schedule is empty. Use /schedule/info for layers and shifts.
  • IDs that do not exist are skipped without error; disabled schedules are included.
  • Callers who cannot edit a schedule (not the account owner or an admin, its creator, or a member of its team) get notify.im values and each webhook’s token, verify_token and sign_secret as empty strings.

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

Request carrying a list of schedule IDs (used by batch info).

schedule_ids
integer<int64>[]
required

Schedule ID list; obtain IDs from POST /schedule/list. At most 100 items per request; split larger sets into several calls. Duplicates are ignored.

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

Response of /schedule/self and /schedule/infos.