Skip to main content
A booking is a scheduled meeting between a host and a client. For fields and response details, see the API reference.

List bookings

This command shows bookings in your workspace. Use this when you want to review upcoming, past, or cancelled bookings.
A member who cannot view the whole workspace’s bookings sees only the bookings they host, plus the ones they booked when their role lets them manage those. --parent-booking-id lists the bookings created together with one booking, such as pre-bookings.
Sample output (--json)

Show a booking

This command shows details for one booking. Use this when you want to inspect client info, host, time zone, and status after finding the booking ID from bookings list.
Required arguments:
  • <id> - Booking UUID or SID
Sample output (--json)

Create a booking

This command creates a new booking. Use this when you want to schedule a meeting on behalf of a client from the terminal.
Sample output (--json)
Pull valid slots first with neetocal meetings slots, then pass one to --slot-date / --slot-start-time. In --quiet mode this prints the new booking id.

Book by phone number, with form answers and add-ons

A meeting that identifies clients by phone does not need --email. Pass --phonenumber in international format instead. Use --form-responses for booking form answers as a JSON object keyed by question field code, --metadata for a JSON object stored on the booking, and --add-on-service-ids for a comma-separated list of the meeting’s add-on service IDs.
On a paid meeting a payment link is sent to the client. Add --reserve-slot to hold the slot without sending a link, or --send-payment-link=false to skip the link.

Book outside availability

Add --override-availability to book a time outside the meeting’s availability. Available hours, minimum notice, buffer time, booking limits, the maximum bookings per slot of a group meeting, holidays, calendar conflicts and existing bookings are ignored. Only a host of the meeting or an admin can do this. Past times are still refused, and a host can’t have two overridden bookings at the same time.
The booking in the output has "is_overridden": true and a bypassed_rules list of the rules that were skipped. On a meeting with several hosts, pass --host-email to choose who gets the booking. To see which times can be booked this way, run neetocal meetings slots with --override-availability.

Update a booking

This command updates a booking. Use this when you need to cancel, approve, reject, or reschedule a booking from the terminal. Reschedule, cancel, approve, or reject a booking. Only the flags you set are sent.
Required arguments:
  • <id> - Booking UUID or SID
Sample output (--json)
Rescheduling keeps the existing client details. Pass --name or --email only to replace them. --override-availability follows the same rules as creating a booking outside availability. The booking keeps its current host. Pass --phonenumber or --metadata to replace the phone number or the metadata when rescheduling.

Create a payment

This command creates a payment record for a booking. Use this when processing payments for paid scheduling links.
Required arguments:
  • <booking-id> - Booking UUID or SID
Pass --idempotency-key to make a retried request return the same payment. For a cash payment on a meeting that has no cash price, pass --amount and, optionally, --currency. The amount defaults to the meeting’s price when it has one, and the currency to the meeting’s price currency or the workspace currency. --tip-value sets a tip as a percentage of the amount.
Sample output (--json)

Update a payment

This command updates a payment for a booking. Use this when you need to mark a payment as successful or rejected.
Required arguments:
  • <booking-id> - Booking UUID or SID
  • <payment-id> - Payment UUID
For a UPI payment marked successful, pass --vpa-address with the VPA that received the payment. With an API key, --performer-id records which team member confirmed the payment.
Sample output (--json)