---
title: "Get Schedules Pending Summary"
method: GET
path: "/events/{event_id}/schedules/pending-summary"
tags: ["Schedule"]
---

# Get Schedules Pending Summary

`GET /events/{event_id}/schedules/pending-summary`

## Request

- Base URL: `https://api.confbuilder.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.confbuilder.com/events/{event_id}/schedules/pending-summary`
- Auth: none declared

ONE call for the publish state of every track on the event.

Per schedule: the draft-vs-latest-published-snapshot diff (same lenient
normalizers as the frontend's useSchedulePendingCounts — ports of their
hash functions, applied server-side where both serializations come from
the same code path, so they never drift), the pending proposal changes
(enriched, ready for the Actions feed), and a minimal activity projection
(id/title/speaker/sponsor ids) for session identity rows.

Replaces the frontend's 2N per-track GET fan-out (versions + activities per
schedule) purely to light up publish dots.

## Path parameters

- `event_id` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/confbuilder/apis/confbuilder-api.md) · [All operations](https://skmtc.dev/confbuilder/apis/confbuilder-api/llms.txt) · [OpenAPI document](https://skmtc.dev/confbuilder/apis/confbuilder-api/revisions/9e576d664e16?raw)