Create a new segment
Creates a new segment using the payload provided
Request body
Example request
{
"name": "beta-users",
"description": "Users willing to help us test and build new features.",
"project": "red-vista",
"constraints": [
{
"contextName": "appName",
"operator": "IN",
"values": [
"my-app",
"my-other-app"
],
"value": "my-app"
}
]
}Response
The resource was successfully created.
Example response
{
"id": 2,
"name": "ios-users",
"description": "IOS users segment",
"constraints": [
{
"contextName": "appName",
"operator": "IN",
"values": [
"my-app",
"my-other-app"
],
"value": "my-app"
}
],
"usedInFeatures": 3,
"usedInProjects": 2,
"project": "red-vista",
"createdBy": "someone@example.com",
"createdAt": "2023-04-12T11:13:31.960Z"
}Changes
Changed in 2 of the 7 revisions of this API.133
- ▲
the
//request property's minLength was increased from0to1request-property-min-length-increased
- ●
added the new
SEMVER_GTEenum value to the//response property for the response statusresponse-property-enum-value-added
- ●
added the new
SEMVER_LTEenum value to the//response property for the response statusresponse-property-enum-value-added
- ○
added the new
SEMVER_GTEenum value to the request property//request-property-enum-value-added
- ○
added the new
SEMVER_LTEenum value to the request property//request-property-enum-value-added
- ▲
- ●
added the new
REGEXenum value to the//response property for the response statusresponse-property-enum-value-added
- ○
added the new
REGEXenum value to the request property//request-property-enum-value-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●