Schedule type. May be ical (used for iCalendar integration), calendar (used for manually created on-call shifts) or web (for web UI managed schedules).
team_id
No
No
ID of the team.
time_zone
No
Yes
Schedule time zone. It is used for manually added on-call shifts in Schedules with type calendar. Default time zone is UTC. For more information about time zones, see time zones. Not used for schedules with type ical.
ical_url_primary
No
If type = ical
URL of external iCal calendar for schedule with type ical.
ical_url_overrides
No
Optional
URL of external iCal calendar for schedule with any type. Events from this calendar override events from primary calendar or from on-call shifts.
enable_web_overrides
No
Optional
Whether to enable web overrides or not. Setting specific for API/Terraform based schedules (calendar type).
slack
No
Optional
Dictionary with Slack-specific settings for a schedule. Includes channel_id and user_group_id fields, that take a channel ID and a user group ID from Slack.
shifts
No
Optional
List of shifts. Used for manually added on-call shifts in Schedules with type calendar.
curl"{{API_URL}}/api/v1/schedules/SBM7DV7BKFUYU/final_shifts?start_date=2023-01-01&end_date=2023-02-01"\--request GET \--header"Authorization: meowmeowmeow"
The above command returns JSON structured in the following way:
Note: The response is paginated. You may need to make multiple requests to get all records.
Caveats
Some notes on the start_date and end_date query parameters:
they are both required and should represent ISO 8601 formatted dates
end_date must be greater than or equal to start_date
end_date cannot be more than 365 days in the future from start_date
Note: you can update schedules affecting past events, which will then
change the output you get from this endpoint. To get consistent information about past shifts
you must be sure to avoid updating rotations in-place but apply the changes as new rotations
with the right starting dates.
Example script to transform data to .csv for all of your schedules
The following Python script will generate a .csv file, oncall-report-2023-01-01-to-2023-01-31.csv. This file will
contain three columns, user_pk, user_email, and hours_on_call, which represents how many hours each user was
on call during the period starting January 1, 2023 to January 31, 2023 (inclusive).
python
import csv
import requests
from datetime import datetime
# CUSTOMIZE THE FOLLOWING VARIABLES
START_DATE ="2023-01-01"
END_DATE ="2023-01-31"
OUTPUT_FILE_NAME =f"oncall-report-{START_DATE}-to-{END_DATE}.csv"
MY_ONCALL_API_BASE_URL ="https://oncall-prod-us-central-0.grafana.net/oncall/api/v1/schedules"
MY_ONCALL_API_KEY ="meowmeowwoofwoof"
headers ={"Authorization": MY_ONCALL_API_KEY}
schedule_ids =[schedule["id"]for schedule in requests.get(MY_ONCALL_API_BASE_URL, headers=headers).json()["results"]]
user_on_call_hours ={}for schedule_id in schedule_ids:
response = requests.get(f"{MY_ONCALL_API_BASE_URL}/{schedule_id}/final_shifts?start_date={START_DATE}&end_date={END_DATE}",
headers=headers)for final_shift in response.json()["results"]:
user_pk = final_shift["user_pk"]
end = datetime.fromisoformat(final_shift["shift_end"])
start = datetime.fromisoformat(final_shift["shift_start"])
shift_time_in_seconds =(end - start).total_seconds()
shift_time_in_hours = shift_time_in_seconds /(60*60)if user_pk in user_on_call_hours:
user_on_call_hours[user_pk]["hours_on_call"]+= shift_time_in_hours
else:
user_on_call_hours[user_pk]={"email": final_shift["user_email"],"hours_on_call": shift_time_in_hours,}withopen(OUTPUT_FILE_NAME,"w")as fp:
csv_writer = csv.DictWriter(fp,["user_pk","user_email","hours_on_call"])
csv_writer.writeheader()for user_pk, user_info in user_on_call_hours.items():
csv_writer.writerow({"user_pk": user_pk,"user_email": user_info["email"],"hours_on_call": user_info["hours_on_call"]})