Screentime.QuietHoursWarning

Emitted 15 minutes before a quiet-hours window starts, such as a bedtime window. Warn the player that play is about to pause so they can reach a save point.

Subscribe your endpoint to this event

k-ID delivers Screentime.QuietHoursWarning only to endpoints subscribed to it, and drops it for the rest without a delivery attempt or an error. Select it for your endpoint on the product's Developer Settings page. See Before you start.

Quiet hours are calendar windows the parent sets, not a usage budget. They apply on the days and at the times configured in the schedule, regardless of how much the player has used today. The paired event when the window actually begins is Screentime.QuietHoursReached.

The 15-minute lead time is fixed in this version and isn't configurable per product.

Fields

Field	Type	Required	Description
eventType	string	yes	Always "Screentime.QuietHoursWarning"
data	object	yes	Quiet hours warning data
data.sessionId	string (UUID)	yes	Session ID the window applies to
data.productId	number	yes	Product ID
data.windowName	string	yes	The parent's name for the window, for example "Bedtime"
data.startsAt	string (RFC 3339)	yes	When the window begins
data.minutesUntilStart	number	yes	Whole minutes until startsAt, clamped at 0

windowName is parent-authored free text. Show it to the player if you want to say which rule is about to apply, but don't switch behavior on its value.

Example

{
  "eventType": "Screentime.QuietHoursWarning",
  "data": {
    "sessionId": "b1a6482d-5242-4b4a-aa88-3fa52595a672",
    "productId": 42,
    "windowName": "Bedtime",
    "startsAt": "2026-06-24T21:00:00+09:00",
    "minutesUntilStart": 15
  }
}

Fires whether or not a session is in flight

Unlike the limit and break-reminder events, quiet-hours events are driven by the parent's calendar rather than by /screentime/start. They fire on their schedule for any player who has a live k-ID session with your product, even when no screentime session is in progress. Handle the event defensively: the player might not be in your product at the time, so don't assume there's a UI to interrupt.

The window boundary is evaluated in the schedule's time zone, so a window that starts at 21:00 fires its warning at 20:45 local time, and the day it belongs to shifts correctly when the lead time crosses midnight.