Skip to main content
POST
Create Core Feature

Authorizations

api_key
string
header
required

Body

application/json

Core Feature creation input

name
string
required

The external name of the core feature (named capability)

Minimum string length: 1
Example:

"Real-time Deal Risk Alerts"

primaryOfferingOId
string
required

Parent Offering (Product, Service, or Solution) this core feature belongs to. A core feature must have exactly one parent offering.

Minimum string length: 1
Example:

"px_123456"

internalName
string

The internal name of the core feature

Example:

"Deal risk engine"

description
string

A description of the core feature

Example:

"Surfaces at-risk deals the moment engagement drops off"

releaseNotesUrls
string<uri>[]

Watched release-notes pages for this core feature; Octave re-reads each on a schedule and proposes library updates from what shipped. Create-only: the list is set here and afterwards managed in the Octave app under Library → core feature → Release notes, so a partial update can never silently drop the rest.

Example:
whatItDoes
string[]

Concrete capabilities this feature delivers

Example:
howItWorks
string[]

How the capability is delivered under the hood

Example:
whatItImpacts
string[]

Outcomes and metrics this feature moves

Example:
whyThisExists
string[]

The problem or gap that justifies this feature

Example:
additionalProperties
object

Workspace-defined additional property values for this core feature, keyed by property key.

Example:

Response

Core Feature created successfully

_metadata
object
required
data
object
required