Features

Validate constraint

Validates a constraint definition. Checks whether the context field exists and whether the applied configuration is valid. Additional properties are not allowed on data objects that you send to this endpoint.

post/api/admin/constraints/validate

Request body

contextNamestring required

The name of the context field that this constraint should apply to.

The operator to use when evaluating this constraint. For more information about the various operators, refer to the strategy constraint operator documentation.

caseInsensitiveboolean

Whether the operator should be case sensitive or not. Defaults to false (being case sensitive).

invertedboolean

Whether the result should be negated or not. If true, will turn a true result into a false result and vice versa.

valuesstring[]

The context values that should be used for constraint evaluation. Use this property instead of value for properties that accept multiple values.

valuestring

The context value that should be used for constraint evaluation. Use this property instead of values for properties that only accept single values.

Example request

{
  "contextName": "appName",
  "operator": "IN",
  "values": [
    "my-app",
    "my-other-app"
  ],
  "value": "my-app"
}

Response

The constraint is valid

Changes

Changed in 2 of the 7 revisions of this API.13

Jul 31, 2026b2c3116e633e12See the full diff
- ▲
  the request property's minLength was increased from 0 to 1
  request-property-min-length-increased
- ○
  added the new SEMVER_GTE enum value to the request property
  request-property-enum-value-added
- ○
  added the new SEMVER_LTE enum value to the request property
  request-property-enum-value-added
Jun 15, 2026774670258f041See the full diff
- ○
  added the new REGEX enum 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

Full history