Reservations

Bookings overlapping a date window. startDate and endDate are required , unlike every other list in this API, this one will not return an unbounded set.

Books a resource, a person, or both.

start and end must carry an explicit UTC offset or Z. A bare local datetime is rejected: it would be read in the server's zone and silently book a different instant than the customer picked.

Which type values you may create depends on your roles , see the Reservation types section. The server also refuses double-bookings and bookings on grounded aircraft.

Pass a recurrence object to create a repeating series. Occurrences are real reservations, so each one can be ramped, reviewed, and invoiced independently.

One booking, with personnel and close-out figures. Invoice totals, Stripe pay links, and paymentOverrides follow the same rule as GET /invoices/{id}: a member does not receive another person's share or rate.

Reschedules or edits a booking. The same clash and role rules as create apply.

Cancels rather than destroys: the booking stays readable with cancelledAt set, which is what keeps cancellation reporting honest. Both fields are required , cancellationCategory is what the report counts, cancellationReason is the detail that makes a count actionable. Get the current list of categories from GET /reports/cancellations/categories; sending a value that isn't on it is rejected.

409 RESERVATION_RAMPED_OUT once the aircraft has left: a flight that has flown cannot be cancelled, because ramp-in has already advanced the aircraft's own Hobbs and tach and cancelling cannot put them back. Void any invoice, reopen the close-out, and correct the readings instead.

Confirms the recorded times. A dual flight needs both seats to confirm before it will invoice, which is why one person cannot occupy two seats on a booking.

Generates the bill for a closed-out flight. Requires the admin role.

Returns an ARRAY. A booking shared between several people produces one invoice PER PAYER , a Stripe invoice bills exactly one customer, so splitting a booking's cost has to be several invoices rather than one invoice with shares underneath it. A booking with one payer returns an array of one.

How the cost divides is set per organization and per booking type , see the cost-splitting rules in the console. With no rules configured, one person is billed for the whole booking, which is how this endpoint has always behaved.

Partial success is possible and is not an error. If the payment processor accepts some invoices and rejects another, the ones that succeeded are real and are returned, with a warnings array naming who could not be billed. Call this endpoint again to bill only the payers who still have no invoice , it will not duplicate the ones already raised. A 400 means nothing was billed at all.

A share below the processor's 50-cent minimum is skipped rather than raised, and reported in warnings.

Records each person's stake in the cost of a booking: their own meter readings when the charge is split by the time each person flew, their percentage when it is split by set shares, or a waiver for somebody who is on the booking but owes nothing (a safety pilot).

Replaces the whole set. Shares have to total 100% across everybody, so merging one person into an existing set is how a total quietly stops adding up. Send everybody every time.

Only people already on the booking may be given a stake. Refused once the booking has been invoiced , the invoices describe the hours and shares they were computed from, and rewriting those underneath them would leave the money disagreeing with its own record.

Whether the shares total 100%, and whether the individual meter readings add up to what the aircraft actually ran, is checked when the booking is INVOICED rather than here , so a half-finished close-out can still be saved.

Records return meter readings and puts the aircraft back on the ramp.

Meter anomaly guard. A reading that looks like a typo, far more digits than the out reading, or hours flown wildly beyond what the booking could have covered, is rejected with 409 and code: "METER_ANOMALY" rather than silently accepted. The response's details.anomalies describes what looked wrong. Resubmit the same body with confirmMeterAnomaly: true once the desk has confirmed the reading is real.

Records departure meter readings and marks the aircraft off the ramp. The first step of closing a flight out.

Clears the sign-offs on a closed-out booking so its times, rates or cost split can be corrected, and the crew re-confirm afterwards.

Nothing else is undone: the readings, the crew and the booked times are left exactly as they are. This is the step that makes the existing correction endpoints reachable again on a booking everybody has already signed off.

Money comes first. A booking with a standing invoice, or an un-reversed ledger charge, is refused with 409 and code: "RESERVATION_BILLED". Void the invoice (or reverse the ledger charge) and call this again. A VOIDED invoice does not block it.

Narrower than correcting. A close-out PIN is a signature, so taking one back off a flight record is limited to the school's staff: an admin, a dispatcher, or the instructor on this booking. A pilot cannot clear another pilot's confirmation. Correcting a reading before anybody has signed needs no such authority. reason is required and is kept on the flight's audit record.

Rewrites a reading already recorded on a flight: Hobbs, tach, or the instruction time on a ground lesson. Only a figure the booking already holds can be corrected, so this opens once the aircraft is back and not before.

Every sign-off on the booking is cleared and the crew confirm the new figures. Clearing a sign-off that is not your own needs the same authority as reopening (an admin, a dispatcher, or the instructor on this booking); re-entering your own PIN afterwards does not. Refused with 409 RESERVATION_BILLED once the flight has been billed: void the invoice (or reverse the ledger charge) first.

A body that matches what is already stored writes nothing. Both first-party forms are prefilled, so an unedited Save is a full echo of the stored figures. That is answered 200 with noChanges: true, and no sign-off is touched.

The aircraft's own meters follow only when this flight is still what they read. Correcting an older booking leaves them alone rather than rolling the aircraft's logbook backwards; the response's meter.followed says which happened, and meter.aircraftHobbs / meter.aircraftTach report what the aircraft still reads so it can be corrected separately.

Two confirmable refusals. 409 METER_ANOMALY when the reading looks like a typo; 409 MAINTENANCE_TRIGGER when saving it would pass an hour-based inspection and ground the aircraft. Resubmit with confirmMeterAnomaly: true / confirmMaintenanceTrigger: true to accept.

Bookings for one aircraft, simulator, or room in a window.

Bookings a person is on, in a window.

Retries raising the Stripe package invoice (or ledger debit) on a prepaid_fixed booking that is already on the calendar. Does not cancel the booking if Stripe fails. Desk staff, the instructor on the booking, or the person who created it. Demo orgs are refused.

Creates the package invoice if it is missing, then marks it paid out of band for cash or a check. Same people who may collect on the booking. Use this when the guest already paid at the desk, or when the package invoice never went out and they are paying by check or cash. Demo orgs are refused.