Trendtracker Connect

Release 0.0.3

Project routes keep published-date start and end, add an optional activeDuring filter, and introduce activity time-series.

Project start and end stay published date, like every other proof-point type. Activity-window overlap is opt-in via activeDuring. Activity-window capital charts move to a new endpoint.

This is an additive change on the project routes introduced in Release 0.0.1. Deprecated /indicators/grants/time-series forwards its chart window onto the new activity time-series endpoint.

Request changes

RouteWhat changed
POST /proof-points/projects/searchOptional activeDuring for [startField, endField] overlap. start / end still filter publishedAt.
POST /proof-points/projects/time-seriesPublished-at histogram again. Optional activeDuring only narrows which projects are counted.
POST /proof-points/projects/activity-time-seriesNew. Calendar buckets over activeDuring.start / activeDuring.end. amountFields are numeric fallbacks (first positive value wins).
POST /proof-points/projects/correlation-matrixOptional activeDuring plus project-specific filters (statuses, programs, …).
POST /proof-points/projects/top-termsSame as correlation.
Other /proof-points/*Unchanged

A missing document endField is treated as ongoing. On the activity time-series route, counts are projects whose interval overlaps each bucket. amount is prorated by how much of that interval sits in the bucket. If amountFields is omitted or empty, each project counts as 1.

activeDuring.start and activeDuring.end are required on activity time-series. Search, correlation, top-terms, and regular time-series treat omitted body start as open and default end to now.

Schemas for these operations are in the OpenAPI spec and the API reference. See Projects for request examples.

On this page