Skip to main content
POST
/
schedule
/
update
Update schedule
curl --request POST \
  --url 'https://api.flashcat.cloud/schedule/update?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "schedule_id": 2001,
  "schedule_name": "Production On-Call (Updated)",
  "description": "Updated primary on-call rotation",
  "team_id": 4291079133131
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

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

Schedule create/update/preview request body. The server accepts the same shape as the schedule detail model; only the key fields are listed here. For update, set schedule_id. For preview, start and end are required.

​
schedule_id
integer<int64>

Schedule ID. Required on update.

​
schedule_name
string

Schedule display name. Max 40 characters.

Maximum string length: 40
​
name
string

Legacy schedule name field. Used when schedule_name is empty.

Maximum string length: 40
​
description
string

Schedule description. Max 500 characters.

Maximum string length: 500
​
team_id
integer<int64>

Owning team ID.

​
layers
object[]

Rotation layers.

​
notify
object

Notification configuration attached to a schedule.

​
start
integer<int64>

Preview window start (Unix seconds, 10 digits). Required for /schedule/preview.

​
end
integer<int64>

Preview window end (Unix seconds, 10 digits). Required for /schedule/preview. Max 45 days after 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

Empty response.