List upcoming agenda hits
Returns upcoming hits for one topic in meeting-time order. Send topicSlug or its legacy alias topic: the request must carry one of them, and topicSlug wins when both are present. A missing or uncovered topic is a 400, so the example request below sends a topic.
Cursor pagination is the default. The legacy page parameter remains available through page 100. Do not send cursor and page together. Cursor responses contain hits and nextCursor, plus totalCount when count=true. Legacy page responses retain hits, totalCount, page, and pageSize. Every successful response includes meta.pagination.
Each hit carries matchId: that is the id GET /api/v1/public/agenda-hits/{matchId} takes, and the recent-hits list does not return ids. An empty hits array is a normal answer — no upcoming classified hit for that topic in the public coverage set right now — and a backend failure returns the same empty page with HTTP 200. Neither is proof that no body meets.
Request
- Base URL: https://aicdapi.com
- URL: https://aicdapi.com/api/v1/public/upcoming-agenda-hits
- Auth: none required
Query parameters
Normalized topic slug. A request needs this or its legacy alias topic; topicSlug takes precedence when both are sent.
Legacy alias for topicSlug. Accepted on its own; topicSlug takes precedence when both are sent.
Opaque cursor returned by the previous response. Do not parse or modify it.
Legacy one-based page number. Omit it to use cursor pagination.
Set to true to include totalCount in a cursor response. Omit otherwise.
Response
Upcoming agenda hits.
Changes
No recorded changes to this operation across all 1 revision of this API.