Plan slot object
Plan slot
The plan slot object represents a recurring posting slot in the authenticated caller's posting plan.
Timezone and local-time semantics
Plan slots store recurring start and end times internally as UTC ISO datetimes, but the public API reads and writes slot times using a durable slot timezone so local wall-clock times remain stable.
Public slot responses return start_time and end_time as local HH:MM values in the slot timezone. The next_occurrence_at field is always an ISO 8601 UTC datetime.
- If
timezoneis provided on create, that timezone is persisted on the slot. - If
timezoneis omitted on create, the owner settings timezone is used. - If no owner timezone is configured,
UTCis used as the fallback. - Legacy slots without a stored timezone still fall back to the owner settings timezone and then
UTC.
| Field | Type | Description |
|---|---|---|
| id | string | Unique slot identifier. |
| start_time | string | Recurring local start time in HH:MM 24-hour format. |
| end_time | string | Recurring local end time in HH:MM 24-hour format. |
| timezone | string | Persisted IANA timezone string for the slot. |
| labels | Label[] | Hydrated label objects in the shape { id, title }. Internal label color is not exposed. |
| recurrence | Recurrence | Recurrence configuration for the slot. |
| next_occurrence_at | string | null | Next future occurrence start datetime in ISO 8601 UTC format. |
| is_active | boolean | Whether the slot is active. Legacy records without this field default to true. |
Recurrence
| Field | Type | Description |
|---|---|---|
| interval | daily | weekly | monthly | Recurrence interval. |
| repeat_every | integer | Repeat frequency. For example, 1 means every interval. |