Endpoint: GET /v1/schedules/meetings

Documentation: https://developer.sky.blackbaud.com/content/favicon-32x32-v1.c216706904f5f5082332b9fe0cfb6a78b5a478c3.pngAPI Reference

Since the 2026-08-31 release added an include_inactive parameter to the roster endpoints (academics, activities, advisories, athletics and community groups) and changed them to return only active sections by default, this affects some of our integrations for getting meetings along with the meeting details and rosters for those meetings. The main issue is that the meetings endpoint did not get the same treatment. It still returns meetings for sections whose offering status is Inactive, and it offers no way to filter them out.

The response gives no way to filter them client side either. The Meeting model carries no offering or section status field, so a caller cannot tell from the response whether a meeting belongs to an inactive section.

The only workaround is a second request to a roster endpoint for the same sections, reading section.offering.status and filtering locally. The concern is not payload size, which is trivial. It is the number of round trips, and the fact that they cannot be avoided or cached away: nothing in the meetings response indicates status, so the lookup has to be repeated on every schedule query.

That lookup costs one extra request per offering type, per school year, per batch of section IDs. A single-day query for one offering type goes from one request to two. Pulling a full school year across all four offering types is roughly 12 meetings requests plus 4 status requests, and a date range spanning two school years adds 8.

The request, in order of preference:

1. Add an include_inactive query parameter to GET /v1/schedules/meetings, using the same name as the roster endpoints.

2. Failing that, add the offering status field to the Meeting model, so callers can filter client side without a second request.

Either option removes the extra round trip. The first also makes the meetings endpoint consistent with the roster endpoints.