booking

Upcoming Meetings

Every demo still ahead, for the Today page.

Frederick, 2026-08-21: "whenever there's an upcoming meeting, it can always be visible on the today page, and then that's where the cancel meeting can be ... one place so you don't have to go into the lead board and do stuff in the lead board."

ALWAYS VISIBLE, WHICH IS WHY IT IS NOT AN ACTION ITEM. A booking already produces a demo_request_booked card, and a card is something a person clears -- resolve it and the meeting stops being visible while remaining entirely real. A meeting that is still coming is a STATE, not a request, and it belongs on the page for as long as it is true. Today is where Rooster pulls a person in, so it is the one place this has to be.

NOT SCOPED TO THE HOST. sales:read sees every upcoming meeting, not only their own: a demo landing on a colleague's calendar while they are on a plane is exactly when somebody else needs to see it, and a spam booking is nobody's. Frederick, on who cancels: "Keith should have it. I should have that ability. Admin should have it. Sales manager should have it. A salesperson should have it."

Cancelled bookings are excluded -- that is what keeping the row rather than deleting it buys: "booked then cancelled" stays a fact without the meeting pretending to still be coming.

get/api/booking/upcoming

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/booking/upcoming
  • Auth: none declared

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.