1.[Fatal errors that require the schedule's data to be corrected and the resolution to restart](#fatal-errors-that-require-the-schedules-data-to-be-corrected-and-the-resolution-to-restart)
2.[Conflict-related errors which can be resolved for each conflict:](#conflict-related-errors-which-can-be-resolved-for-each-conflict)
6.[Read more](#read-more)
# API: Schedules and conflict resolution
This document outlines handling conflict resolution using the API.
Find an overview of the API spec at [api.aura.radio](https://api.aura.radio).
To learn about conflict resolution check out [Timeslot Collision Detection](../../user/timeslot-collision-detection.md) in the User Guide.
## Overview
Creating timeslots is only possible by creating/updating a schedule.
When creating/updating a schedule by giving the schedule data:
...
...
@@ -224,10 +207,3 @@ Possible error messages are:
The solution has a value which is not part of `solution_choices`. Provide a value of
`solution_choices` (at least `"ours"` or `"theirs"`)