Skip to main content
POST
/
v1
/
features
Create feature
curl --request POST \
  --url https://api.hyperline.co/v1/features \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "code": "sso",
  "name": "Single sign-on",
  "value_type": "boolean",
  "default_value": false,
  "description": "Allow users to authenticate with SAML SSO."
}
'
{
  "code": "sso",
  "name": "Single sign-on",
  "description": "Allow users to authenticate with SAML SSO.",
  "resolution_strategy": null,
  "default_value": false,
  "status": "active",
  "created_at": "2024-12-20T16:04:11Z",
  "updated_at": "2024-12-20T16:04:11Z",
  "archived_at": null
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Feature creation payload.

​
code
string
required

Feature code.

Required string length: 1 - 100
Pattern: ^[a-z0-9][a-z0-9_-]*$
Example:

"sso"

​
name
string
required

Feature name.

Minimum string length: 1
Example:

"Single sign-on"

​
value_type
enum<string>
required

Type of feature value.

Available options:
boolean
​
default_value
boolean
required

Default value used when no product or customer feature value applies.

Example:

false

​
description
string | null

Feature description.

Example:

"Allow users to authenticate with SAML SSO."

Response

201 - application/json
​
code
string
required

Feature code.

Example:

"sso"

​
name
string
required

Feature name.

Example:

"Single sign-on"

​
description
string | null
required

Feature description.

Example:

"Allow users to authenticate with SAML SSO."

​
value_type
enum<string>
required

Type of feature value.

Available options:
boolean,
number
​
resolution_strategy
enum<string> | null
required

Strategy used to combine multiple product feature values for number features.

Available options:
max,
sum,
replace
Example:

null

​
default_value
required

Default value used when no product or customer feature value applies.

Example:

false

​
status
enum<string>
required

Feature status.

Available options:
active,
archived
Example:

"active"

​
created_at
string<date-time>
required

Creation date.

Example:

"2024-12-20T16:04:11Z"

​
updated_at
string<date-time>
required

Last update date.

Example:

"2024-12-20T16:04:11Z"

​
archived_at
string<date-time> | null
required

Archival date.

Example:

null