Schedule Tools – Time Interval Merger

Choose this endpoint when you have a raw list of date-time intervals (possibly overlapping, adjacent, or duplicated) and need a canonical, minimal, non-overlapping representation — especially for calendar aggregation, busy-time computation, billing calculations, or scheduling pipelines that require clean interval sets. Prefer it over manual logic when working with RFC 3339 timestamps across timezones where arithmetic errors are risky.

• Invalid RFC 3339 format in any interval boundary returns a 400 error
• End datetime before start datetime in any interval causes a validation error
• Empty input list returns an empty merged list or error depending on implementation
• Intervals with mismatched timezone representations may cause unexpected merging behavior
• Malformed JSON body returns a 400 bad request