Typed DTOs

The fluent builder is the shortest way to book, but every write underneath takes a typed DTO. Pass them yourself from imports, API endpoints or queued jobs — through the facade, an injected AppointmentManager or an action (see DI and actions).

AppointmentData

create(), createRecurring() and CreateAppointmentAction take an AppointmentData — the fluent builder produces exactly this DTO under the hood:

use Carbon\CarbonImmutable;
use RoundlyConsulting\Appointments\DataTransferObjects\AppointmentData;
use RoundlyConsulting\Appointments\DataTransferObjects\ParticipantData;
use RoundlyConsulting\Appointments\Enums\ParticipantRole;
use RoundlyConsulting\Appointments\Facades\Appointments;

$appointment = Appointments::create(new AppointmentData(
    name: 'Project kickoff',
    startsAt: CarbonImmutable::parse('2026-07-01 17:30'),
    durationMinutes: 90,
    participants: [
        new ParticipantData($host, ParticipantRole::Organiser),
        new ParticipantData($guest),
    ],
));

ParticipantData

One per participant: new ParticipantData(Model $participant, ?ParticipantRole $role = null, ?array $meta = null). Any Eloquent model can be the participant. AttachParticipantAction takes one too.

RecurrenceData

createRecurring() and ScheduleRecurringAppointmentAction take a RecurrenceData rule — its fields are listed in Recurring appointments. create() ignores AppointmentData::$recurrence; createRecurring() falls back to it when you pass no rule.

Validated on construction

Both DTOs refuse values that can’t describe a booking, before anything is written: an AppointmentData with a durationMinutes below one throws InvalidScheduleException, and a RecurrenceData with an interval or count below one, or a weekday outside 1–7, throws InvalidRecurrenceException.