am-capture3

auth7

board6

boardroom7

booking11

briefing5

chairman10

commissions7

commitments4

company1

consumer-accounts18

contractor-onboarding-public5

contractors23

customer_service69

customer-search6

decisions5

equipment34

finance106

finance-bank22

floor5

floor-blocks21

floor-blocks-public4

floor-blocks-tubs4

floor-clock4

floor-day-cutoff1

floor-design-review2

floor-done1

floor-payouts9

floor-station2

fulfillment40

gitlab1

growth-strategies11

hr-policies1

industry6

investor6

issues16

live1

locke-booking6

manufacturing2

metrics13

org_documents18

orgs31

platform8

platform-admin30

postage13

print39

print-agent7

public-demo-request5

public-return-mail3

repairs6

return-mail9

rooster100

rooster-cases6

rooster-executive-turns3

rooster-floor-turns4

rooster-instructions3

rooster-mcp1

rooster-qa1

rooster-reflex1

rooster-supervision8

rooster-team-chat10

sales105

shifts2

sms2

system42

today2

tracking2

transcription17

vendor-registration-public3

voice53

vouched-webhook1

workforce35

booking

Missed Next Steps

The manager-facing missed-next-steps list (GitHub issue #2319, Frederick 2026-09-14, R-154; PLAN-ACTIVE-TODAY-CARDS-SETTLE-001.md §F).

Scoped to the CALLER: their own direct reports' missed attestable next steps, plus any that never got a confident name at all (visible only if the caller holds the founder pool's own grant) -- see meeting_next_steps_service.missed_next_steps_for's own docstring for the exact rule. Same authentication posture as /team-meeting/agenda above (any authenticated principal may call this; the SCOPING, not a route-level grant, is what keeps a manager from seeing another manager's reports) -- a manager with no reports and no founder-pool grant gets back an empty, honest list, never a 403.

get/api/booking/missed-next-steps

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/missed-next-steps
Auth: none declared

Response

Successful Response

object required

Changes

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