Skip to main content
Silent hours rules tell the platform when to hold non-urgent alerts rather than immediately paging team members. This is useful for protecting engineers outside business hours without disabling notifications entirely. Each rule targets a specific team, specifies a time range and timezone, and can be scoped to selected days of the week. All requests require a Bearer token in the Authorization header.

List all silent-hours rules

GET https://your-api-domain.com/api/v1/silent-hours Returns all silent-hours rules configured for the business.

Response fields

object[]
required
Array of silent-hours rule objects.

Replace all silent-hours rules

POST https://your-api-domain.com/api/v1/silent-hours
This endpoint replaces all existing silent-hours rules for the business with the set provided in the request body. Any rules not included in the payload will be permanently deleted. To preserve existing rules, retrieve them first with GET /silent-hours, modify the array, and re-submit.
Submits a complete, authoritative list of silent-hours rules. The operation is atomic: the entire set is replaced in a single transaction.

Request body

object[]
required
The complete list of silent-hours rules to activate. Replaces all current rules.

Response fields

object[]
required
The full set of rules now active, each with a server-assigned id.

Update a rule

PUT https://your-api-domain.com/api/v1/silent-hours/:id Updates a single existing silent-hours rule by ID. Supply the full rule body; all fields are replaced.

Path parameters

string
required
The unique identifier of the rule to update.

Request body

Accepts the same fields as the individual rule objects in Replace all rules.

Delete a rule

DELETE https://your-api-domain.com/api/v1/silent-hours/:id Removes a single silent-hours rule. Other rules are unaffected.

Path parameters

string
required
The unique identifier of the rule to delete.