position: 1 layer first. If that layer does not acknowledge within ackTimeoutMinutes, it moves to position: 2, and so on.
Layers are sub-resources of policies. All layer endpoints require the parent
policyId in the path. To manage the policy itself, see Policies.Layer targets
Each layer has atarget that specifies who to notify. The target field is a discriminated union on type:
POST /escalation/policies/{policyId}/layers
Add a layer to an escalation policy. You can specify the position to insert the layer at a particular point in the escalation sequence.
Path parameters
The UUID of the policy to add the layer to.
Request body
1-based position of this layer in the escalation sequence. Position
1 is notified first. Must be a positive integer.Number of minutes to wait for an acknowledgment before escalating to the next layer. Minimum
1, maximum 10080 (7 days).The notification target for this layer. Must be one of:Schedule target — notify the current on-call for a schedule:Users target — notify specific users directly:
Response fields
The created policy layer.
Error codes
PATCH /escalation/policies/{policyId}/layers/{layerId}
Update one or more fields on an existing policy layer. All fields are optional — only the fields you include are updated.
Path parameters
The UUID of the parent escalation policy.
The UUID of the layer to update.
Request body
Updated acknowledgment timeout in minutes. Minimum
1, maximum 10080.Updated notification target. Replaces the existing target entirely. Must be a valid
schedule or users target object.Response fields
The updated policy layer object.
Error codes
DELETE /escalation/policies/{policyId}/layers/{layerId}
Remove a layer from an escalation policy. This action is permanent.
Path parameters
The UUID of the parent escalation policy.
The UUID of the layer to delete.
Response fields
true when the layer was deleted.Error codes
PUT /escalation/policies/{policyId}/layers/order
Reorder all layers in a policy by providing the complete ordered list of layer IDs. The first ID in layerIds becomes position: 1, the second becomes position: 2, and so on.
You must include every layer ID that belongs to the policy — partial lists are rejected.
position determines the escalation order — layer at position: 1 is always notified first. Reordering layers directly changes who gets paged and when during an active incident response.Path parameters
The UUID of the escalation policy whose layers you want to reorder.
Request body
Complete ordered list of layer IDs in the desired escalation sequence. Must include all existing layer IDs for this policy — no more, no fewer. Accepts 1–50 IDs.
Response fields
The full list of policy layers in their new order, with updated
position values.