Update
Update a sync ruleβs sync_type and permanent members in place. If the ruleβs sync target is shared with other schedules, a sync_type change propagates to every linked schedule and the entire operation aborts if the caller lacks edit permission on any of them. Permanent members are scoped to this rule and never propagate.
schedule_sync_rules.update scope.Authorizations
API key from your incident.io dashboard (Settings β API keys)
Path Parameters
The parent schedule ID
"01FDAG4SAP5TYPT98WGR2N7W91"
The sync rule ID
"01JXYZ000000000000000000CD"
Body
Which schedule members sync to the user group
on_call, all_users "on_call"
Annotations that track metadata about this resource
IDs of users to always keep in the Slack user group, regardless of who is on call. Each must be an active user in your organisation. Replaces the rule's current permanent members: pass an empty array to remove them all, or omit the field to leave them unchanged.
Response
OK response.
A sync rule links a schedule to a sync target, telling us which of the schedule's members should flow into the target's Slack user group.
sync_type decides who is synced: on_call syncs only the people currently on call, while all_users syncs everyone on the schedule. By default every rotation on the schedule is included; set rotation_id to scope the rule to a single rotation. As the schedule's shifts change hands, we keep the target's Slack user group membership in step with the rule.
permanent_member_user_ids names users who stay in the group whichever way the shifts fall, on top of whoever sync_type selects.