Update a time condition

Updates a time condition in place; fields you omit keep their current values, while conditions is replaced wholesale by whatever array you send. Send expected_update_date to avoid clobbering a concurrent change — a mismatch fails with 409 and code: "stale" instead of writing. A condition owned by a call flow cannot be edited here and returns 409. Sending no body at all (or a body that is not valid JSON) is not an error: it instead drops expired holiday rules from the live routing, leaving the stored conditions array untouched, and returns {"success": true}. The record and its routing entry are written separately, so a failure part-way through leaves no rollback.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

ID of the time condition to update.

Body Params
string

New name for the condition; omit to keep the current one.

string | null

New description, or null to clear it; omit to keep the current one.

conditions
array

Replacement list of rules, each pairing a match (dates, days and times) with an action (where matching calls go); this replaces the whole list, and null is treated as an empty list.

conditions
closed_action
object | null

Replacement action for calls that match none of the conditions; omit to keep the current one.

string

Identifier of the routing entry this condition drives; a different value must belong to your account or the request is rejected with 403.

string

New extension number for the condition; 10000–19999 is reserved and rejected.

string

The update_date you last read back; if the record has changed since, the update is refused instead of overwriting it.

string

Legacy field: any non-empty value here suppresses the legacy-record creation path below. It does not change which record the path id updates.

boolean

Legacy field: when true and no id is sent in the body, the condition is recreated as a current record and its old routing details are removed; the new ID is not returned.

Responses

401

Missing or invalid API key.

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json