KOkobaltlabs
contract-lifecycle-settings

Get Contract Lifecycle Settings

When this company is reminded about a renewal decision, and who is.

Always concrete values: a company that has never saved gets the code defaults with is_configured=False — a starting point for the form, not a policy in force, since nothing is scheduled until the PUT below creates the row.

get/contract-lifecycle-settings

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/contract-lifecycle-settings
  • Auth
    none declared

Response

Successful Response

is_configuredboolean required
notice_reminder_lead_daysinteger[] required
renewal_reminder_lead_daysinteger[] required
notice_reminders_enabledboolean
renewal_reminders_enabledboolean
default_notice_period_valueinteger nullable
default_notice_period_unit'days' | 'months'

Unit of a termination-notice period.

Months are not 30 days: 3 months before 2026-05-31 is 2026-02-28, while 90 days before it is 2026-03-02. This generates a legal deadline, so the unit is stored rather than normalized to days (see backend.helpers.contract_terms.derive_notice_date).

default_renewal_term_monthsinteger required
available_assignee_modesAssigneeMode[]
default_assignee_mode'vendor_assignees' | 'user' | 'team' required

How responsibility for an entity is resolved to a set of users.

Not every mode is valid for every entity — see ASSIGNEE_SCOPES.

Changes

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