Fetch the active milestones for a Tiltify fundraising event.
Proxy-only. Tiltify's public REST API has no fundraising-event
milestones route — this is served by the PLAY LIVE Tiltify proxy,
which resolves them off the GraphQL fact graph. Requires
tiltify.UseProxy() to have been applied — which
configure does automatically once tiltifyProxyUrl is set.
A direct v5api.tiltify.com base URL will 404 and resolve to [].
Scoped to St. Jude fundraising events — the proxy rejects any other
cause's event with a 403.
Errors are swallowed to [], matching every other fetcher here. That
means a malformed id (proxy 422), a non-St.-Jude event (403), and an
unknown event (404 → null) are all indistinguishable from "this
event has no active milestones". Callers that need to tell them apart
should call tiltify.GetActiveFundraisingEventMilestones directly —
it preserves null for a missing event and throws on 422/403.
Fetch the active milestones for a Tiltify fundraising event.
Proxy-only. Tiltify's public REST API has no fundraising-event milestones route — this is served by the PLAY LIVE Tiltify proxy, which resolves them off the GraphQL fact graph. Requires
tiltify.UseProxy()to have been applied — which configure does automatically oncetiltifyProxyUrlis set. A directv5api.tiltify.combase URL will 404 and resolve to[].Scoped to St. Jude fundraising events — the proxy rejects any other cause's event with a 403.
Errors are swallowed to
[], matching every other fetcher here. That means a malformed id (proxy 422), a non-St.-Jude event (403), and an unknown event (404 →null) are all indistinguishable from "this event has no active milestones". Callers that need to tell them apart should calltiltify.GetActiveFundraisingEventMilestonesdirectly — it preservesnullfor a missing event and throws on 422/403.