Feature Request / API Limitation: Missing all_day parameter in Calendar Events REST API

Feature Request / API Limitation: Missing all_day parameter in Calendar Events REST API (POST /calendar/events)

(Regarding V5.X hosted solution)

When creating calendar events through the frontend web UI, the form submission includes event_dates[all_day] = 1, which correctly flags the event as an all-day event and suppresses time display (12:00 AM – 11:59 PM) on the rendered calendar view.

However, when creating events via the REST API endpoint (POST /calendar/events), there is no equivalent payload parameter (all_day, allday, or nested form support) to set this flag. Consequently, all API-created events default to rendering time bounds (12:00 AM to 11:59 PM) even when providing midnight-to-midnight UTC ranges.

Question:

1. Is there an undocumented flat parameter or endpoint mechanism in the current REST API schema to pass an all-day boolean flag for calendar events?

2. If not, can this be considered for a future update to parity-match the REST API schema with the internal event_dates[all_day] form controller?

Edited Saturday at 7:18 PM1 day by LivingMonolith