Release a digest early
Send a digest now instead of waiting for its scheduled time, so your users get what they have collected so far right away.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the digest schedule to release. Newer schedules are sch_01m26xfcn3endt3nxy4e2kx2rh and need no encoding. Schedules created before that format are sch/{uuid} and contain a literal /, so those must be URL-encoded (e.g. sch%2F00000000-0000-0000-0000-000000000000). Both forms remain valid; existing ids are never migrated.
Response
The digest schedule was released. A 204 is also returned when the schedule exists but currently holds no in-progress digest instances to release, so the call is safe to repeat. A schedule ID that does not exist is a 404 rather than a 204, so "nothing to release" and "no such schedule" answer differently.