KOkobaltlabs
thirdparties-key-dates

Ratify Key Date

Promote a PROPOSED key date to ACTIVE, scheduling reminder notifications.

If the proposal replaces an existing key date, that target is marked SUPERSEDED and its unsent notifications are purged.

post/thirdparties/key-dates/{key_date_id}/ratify

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/thirdparties/key-dates/{key_date_id}/ratify
  • Auth
    none declared

Path parameters

key_date_idstring uuid required

Request body

lead_daysinteger[]
labelstring nullable
key_date_type'termination_notice' | 'renewal' | 'review' | 'other'
monthinteger nullable
dayinteger nullable
first_yearinteger nullable
interval_yearsinteger nullable

Response

Successful Response

key_date_idstring uuid required
status'proposed' | 'active' | 'superseded' required

Lifecycle of a key date.

Distinct from the AnnualKeyDates.active boolean, which only toggles notifications on an already-real key date. An ACTIVE-status key date may still have active=False notifications.

messagestring

Changes

No recorded changes to this operation across all 8 revisions of this API.