Altostrat Studio is here — the AI-native network operations IDE for engineers running production. Terminal, diagrams, runbooks, and Copilot in one workspace. Get started →
curl --request POST \
--url https://v1.api.altostrat.io/chrono/schedules \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "Weekend Maintenance Window",
"hours": [
{
"day": "saturday",
"start": "22:00",
"end": "23:59"
}
],
"timezone": "America/New_York",
"metadata": [
{
"key": "ticket_ref",
"value": "JIRA-456"
}
]
}
'{
"id": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
"name": "Business Hours Policy",
"timezone": "Australia/Sydney",
"active": true,
"updated_at": "2025-10-29T01:43:31Z",
"created_at": "2025-10-29T01:43:31Z",
"hours": [
{
"day": "monday",
"start": "09:00",
"end": "17:00"
}
],
"metadata": [
{
"key": "policy_id",
"value": "pol_12345"
}
]
}Creates a new schedule with a defined set of recurring time slots. Upon creation, the schedule’s active status is automatically calculated based on the current time and the provided slots.
curl --request POST \
--url https://v1.api.altostrat.io/chrono/schedules \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "Weekend Maintenance Window",
"hours": [
{
"day": "saturday",
"start": "22:00",
"end": "23:59"
}
],
"timezone": "America/New_York",
"metadata": [
{
"key": "ticket_ref",
"value": "JIRA-456"
}
]
}
'{
"id": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
"name": "Business Hours Policy",
"timezone": "Australia/Sydney",
"active": true,
"updated_at": "2025-10-29T01:43:31Z",
"created_at": "2025-10-29T01:43:31Z",
"hours": [
{
"day": "monday",
"start": "09:00",
"end": "17:00"
}
],
"metadata": [
{
"key": "policy_id",
"value": "pol_12345"
}
]
}Documentation Index
Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Enter your API key in the format: Bearer {key}
The details of the schedule to create.
The request body for creating or updating a schedule.
The name of the schedule. Must be unique within your workspace.
200"Weekend Maintenance Window"
An array of time slot objects. This array will completely replace any existing time slots on an update.
50Show child attributes
An IANA Time Zone Database name, e.g., America/New_York or UTC. If not provided, the workspace default will be used.
"America/New_York"
An array of key-value pairs. On update, provide a key with a null value to delete it. New keys will be added, and existing keys will be updated.
50Show child attributes
The schedule was created successfully.
Represents a schedule object that defines when a policy or configuration is active.
The unique identifier for the schedule.
"9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d"
A human-readable name for the schedule.
"Business Hours Policy"
The IANA timezone identifier that this schedule operates in. All start and end times are relative to this timezone.
"Australia/Sydney"
A read-only flag indicating whether the schedule is currently within an active time slot. This is calculated by the system.
true
The timestamp of when the schedule was last updated.
"2025-10-29T01:43:31Z"
The timestamp of when the schedule was created.
"2025-10-29T01:43:31Z"
A list of time slots that define the active periods for this schedule.
Show child attributes
A list of key-value pairs that can be used to store additional information about the schedule.
Show child attributes
Was this page helpful?