API Reference: Nullable field corrections

April 9, 2026Platform

Fixed

Updated OpenAPI specs to correctly document fields that can return null from the API. Previously these were typed as plain boolean, string, integer, or array, which caused typed client generation to break when null values appeared.

For each nullable field, the description now explains what null means and what default to treat it as (for example, “treat null the same as false”).

Scheduler API (8 fields)

• event_booking.disable_emails, hide_participants, notify_participants — boolean or null
• requires_session_auth — boolean or null
• slug — string or null
• appearance — object or null
• min_booking_notice — integer or null
• Group configurations: same fields where applicable

Events API (5 fields)

• busy — boolean or null
• reminders.use_default — boolean or null
• reminders.overrides — array or null
• calendar_id — string or null
• when — object or null

Contacts API (6 fields)

• emails, groups, im_addresses, phone_numbers, physical_addresses, web_pages — all array or null

Availability / Free-Busy (3 fields)

• time_slots (availability and free/busy responses) — array or null
• emails (time slot) — array or null

Attachments API

• Restored missing is_inline boolean field