GET /tms/bookings/{id}/billing-readiness

TMS > tms.booking

What it does

/tms/bookings/{id}/billing-readiness accepts GET and is declared in app/systems/TMS/booking/api_routes.php:1688 as a pattern route matching /tms/bookings/(?P<id>[0-9a-fA-F-]{36}|\d+)/billing-readiness.

The handler is an inline closure declared in the route table, so the behaviour is in the declaring file rather than in a separate helper. It resolves the route id with tmsBookingApiResolveRouteId() and delegates to booking_billing_readiness_projection().

The id path segment accepts either a UUID or a numeric id.

Who calls it

No literal caller path was found. The handler is reached through the booking screens that ask whether a booking can be billed.

Notes

• This page was missing while the route existed in the code. It was written from the route entry; the tables reached and the SQL are not restated here because they were not read for this endpoint.