Base URLhttp://0.0.0.0:33031Spechttp://0.0.0.0:33031/docs/openapi.jsonCommandstrunhttp://0.0.0.0:33031/docs/openapi.json--urlhttp://0.0.0.0:33031--report-html-pathschemathesis-report--max-time3600--request-timeout30--continue-on-failure--no-shrink--suppress-health-checkall--output-sanitizefalseSeed114964124404399321992191656600184532338Phases
{"id":"76247e16-0f41-4611-8e6c-b6abab625eb3","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/features/checkout/tags
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - value: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Tag type '0000000000000000000000000000000000000000000000000' does not exist","details":[{"message":"Tag type '0000000000000000000000000000000000000000000000000' does not exist"}]}
{"name":"NameExistsError","message":"A context field with that name already exist","details":[{"message":"A context field with that name already exist"}]}
{"id":"32a58b05-9ba0-4a1b-a00a-6167e0b40f48","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/context
{"id":"fda845d6-6453-47f9-83bf-b4e513430828","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"/body/name","message":"The `/body/name` property is required. It was not present on the data you sent."}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" must be URL friendly. You provided \"L9Eu\"."}]}
{"name":"UnknownError","message":"insert into \"context_fields\" (\"description\", \"legal_values\", \"name\", \"project\", \"sort_order\", \"stickiness\") values (DEFAULT, $1, $2, $3, $4, $5) returning * - value \"-1954426799556\" is out of range for type integer","details":[{"message":"insert into \"context_fields\" (\"description\", \"legal_values\", \"name\", \"project\", \"sort_order\", \"stickiness\") values (DEFAULT, $1, $2, $3, $4, $5) returning * - value \"-1954426799556\" is out of range for type // Output truncated...
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"undefined","message":"The root object of the request body does not allow additional properties. Your request included the `undefined` property."}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - constraints -> Array with invalid items: value: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"constraints[0].values[0]\" is not allowed to be empty."}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - type: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"type\" must be URL friendly. You provided \"îøü|}uÔ\"."}]}
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Project=project-851 does not exist","details":[{"message":"Project=project-851 does not exist"}]}
{"name":"UnknownError","message":"SELECT EXISTS (SELECT 1 FROM environments WHERE name = $1) AS present - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"SELECT EXISTS (SELECT 1 FROM environments WHERE name = $1) AS present - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
{"id":"75be7251-58ad-4c49-b30a-80f6d06299fe","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/context
{"id":"d2055da6-8f32-42ab-bdd1-bd1c7c6bebe7","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"/body/name","message":"The `/body/name` property is required. It was not present on the data you sent."}]}
{"name":"NameExistsError","message":"A context field with that name already exist","details":[{"message":"A context field with that name already exist"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" must be URL friendly. You provided \"Rollout percentage\"."}]}
{"id":"dd060808-71f8-411e-819d-06fe5a6ad392","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/environments/sort-order
{"id":"4fb6bb65-afc8-4a11-958f-5424e3dcd033","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/x-schemathesis-additional` property must be integer. You sent {}.","path":"/body/x-schemathesis-additional"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - object with invalid additional property: Incorrect type
{"name":"UnknownError","message":"update \"environments\" set \"sort_order\" = $1 where \"name\" = $2 - value \"-44587497029\" is out of range for type integer","details":[{"message":"update \"environments\" set \"sort_order\" = $1 where \"name\" = $2 - value \"-44587497029\" is out of range for type integer"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 5 additional properties not defined in the schema (``, `æ𤂧
ow `, `𢷻ú¾h}eþ` and 2 more). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"value\" must be a safe number. You provided -32589158477190046000."}]}
{"id":"6801a0b0-ab99-46b8-939b-6dad7817be48","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/playground/advanced
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - context -> userId: Incorrect type
Response200 OK
{"features":[],"input":{"environments":["development","production"],"projects":[],"context":{"appName":"My cool application.","currentTime":"2022-07-05T12:56:41+02:00","environment":"","properties":{"customContextField":"this is one!","otherCustomField":"3"},"remoteAddress":"192.168.1.1","sessionId":"b65e7b23-fec0-4814-a129-0e9861ef18fc","userId":""}}}
Additional properties are not allowed ('hasUnsatisfiedDependency' was unexpected)
Validated against the response schema for status code 200.
Schema at /components/schemas/advancedPlaygroundEnvironmentFeatureSchema:
{
"additionalProperties": false,
"description": "A simplified feature flag model intended for the Unleash ...
"type": "object",
"required": [
"name",
"environment",
"context",
"projectId",
"isEnabled",
"isEnabledInCurrentEnvironment",
"variant",
"variants",
"strategies"
],
"properties": {
"name": {
"type": "string",
"example": "my-feature",
// Output truncated...
}
Value:
{
"context": {
"appName": "My cool application.",
"currentTime": "2022-07-05T12:56:41+02:00",
"customContextField": "this is one!",
"environment": "",
"otherCustomField": "3",
"remoteAddress": "192.168.1.1",
"sessionId": "b65e7b23-fec0-4814-a129-0e9861ef18fc",
"userId": "username@provider.com"
},
"environment": "development",
"hasUnsatisfiedDependency": false,
"isEnabled": true,
"isEnabledInCurrentEnvironment": true,
"name": "search",
"projectId": "default",
"strategies": {
"data": [
// Output truncated...
}
{"enabled":false,"featureEnabled":true,"feature_enabled":true,"name":"disabled"} is not valid under any of the schemas listed in the 'anyOf' keyword
Validated against the response schema for status code 200.
Schema at /components/schemas/advancedPlaygroundEnvironmentFeatureSchema/properties/variant:
{
"anyOf": [
{
"description": "The feature variant you receive based on the prov...
"type": "object",
"additionalProperties": false,
"required": [
"name",
"enabled"
],
"properties": {
"name": {
"type": "string",
"description": "The variant's name. If there is no varian...
"example": "red-variant"
},
"enabled": {
"type": "boolean",
"description": "Whether the variant is enabled or not. If...
// Output truncated...
}
Value:
{
"enabled": false,
"featureEnabled": true,
"feature_enabled": true,
"name": "disabled"
}
Response200 OK
{"features":[{"name":"search","projectId":"default","environments":{"development":[{"isEnabled":true,"isEnabledInCurrentEnvironment":true,"hasUnsatisfiedDependency":false,"variant":{"feature_enabled":true,"featureEnabled":true,"name":"disabled","enabled":false},"context":{"currentTime":"2022-07-05T12:56:41+02:00","environment":"","customContextField":"this is one!","otherCustomField":"3","remoteAddress":"192.168.1.1","sessionId":"b65e7b23-fec0-4814-a129-0e9861ef18fc","userId":"username@provider.com","appNam // Output truncated...
{"name":"UnknownError","message":"select \"features\".\"name\" as \"name\", \"features\".\"description\" as \"description\", \"features\".\"type\" as \"type\", \"features\".\"project\" as \"project\", \"features\".\"stale\" as \"stale\", \"features\".\"impression_data\" as \"impression_data\", \"features\".\"created_at\" as \"created_at\", \"fe\".\"variants\" as \"variants\", \"fe\".\"enabled\" as \"enabled\", \"fe\".\"environment\" as \"environment\", \"fs\".\"id\" as \"strategy_id\", \"fs\".\"strategy_nam // Output truncated...
{"id":"dc4e9c01-329e-464d-b0c4-5120fd2f6648","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/environments/development/default-strategy
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - segments -> Array with invalid items: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Only \"flexibleRollout\" strategy can be used as a default strategy for an environment","details":[{"message":"Only \"flexibleRollout\" strategy can be used as a default strategy for an environment"}]}
{"name":"disable-comments","description":"Controls disabling of the comments section in case of an incident","type":"release","project":"default","stale":false,"createdAt":"2026-10-19T21:09:10.213Z","impressionData":false,"archived":false}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"name": "disable-comments", "type": "release", "description": "Controls disabling of the comments section in case of an incident", "impressionData": false, "tags": [{"value": "a-tag-value", "type": "simple", "color": "#FFFFFF"}]}' http://0.0.0.0:33031/api/admin/projects/default/features
{"id":"767405df-d3de-4919-a7d0-8b5145ef1df1","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/tags/0/color` property must match pattern \"^#[0-9A-Fa-f]{6}$\". You sent \"AAA\".","path":"/body/tags/0/color"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 3 additional properties not defined in the schema (` Ê`, `ñôËeP`, `«/Ù`). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" must be URL friendly. You provided \"ôa#Â𐐙\\u0012\\u0010î¨\"."}]}
{"id":"34947b98-e6e5-4b49-9b35-22decb010977","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/0/from` property must be string. You sent {}.","path":"/body/0/from"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - array with invalid items: from: Incorrect type
Response200 OK
{"name":"checkout","description":"Controls disabling of the comments section in case of an incident","type":"kill-switch","project":"default","stale":true,"createdAt":"2026-10-19T21:09:07.620Z","impressionData":false,"archivedAt":"2026-10-19T21:09:35.265Z","archived":true}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"type\" must be a string."}]}
{"id":"be036a79-3326-44b8-80ec-b87bbf023acd","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/tags/removedTags/0/color` property must match pattern \"^#[0-9A-Fa-f]{6}$\". You sent \"AAA\".","path":"/body/tags/removedTags/0/color"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - tags -> removedTags -> Array with invalid items: type: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Tag type '00' does not exist","details":[{"message":"Tag type '00' does not exist"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 1 additional property not defined in the schema (`{Ô-~0M`). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Strategies may not have more than 5 segments","details":[{"message":"Strategies may not have more than 5 segments"}]}
{"id":"e1282d44-5fa5-4b57-9cc8-0df541e57d82","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"null,null\".","path":"/params/id"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Invalid project. Segment is being used by strategies in other projects: default","details":[{"message":"Invalid project. Segment is being used by strategies in other projects: default"}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"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", "caseInsensitive": false, "inverted": false}]}' http://0.0.0.0:33031/api/admin/segments/1
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"\u00ab\u00eeg\u00a9\u0016": [], "\u00c6": [], "": {"\b\u0000\u0093\u00ff\u00e9\u00ecO.\u00bd\u00b8\u00f8\ub5b1": null}, "description": "All Datadog tags added to a specific feature are sent to datadog event stream.", "constraints": [], "project": "0", "name": "\u00e3"}' http://0.0.0.0:33031/api/admin/segments/7
{"id":"66aa2d57-a59e-4668-ab71-7f0890246842","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/parameters/0/required` property must be boolean. You sent {}.","path":"/body/parameters/0/required"}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"description": "Enable the feature for users who have not logged in before.", "parameters": [{"name": "Rollout percentage", "type": "percentage", "description": "How many percent of users should see this feature?", "required": {}}]}' http://0.0.0.0:33031/api/admin/strategies/false
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - parameters -> Array with invalid items: required: Incorrect type
Response200 OK
<EMPTY>
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"description": "Enable the feature for users who have not logged in before.", "parameters": [{"name": "Rollout percentage", "type": "percentage", "description": "How many percent of users should see this feature?", "required": null}]}' http://0.0.0.0:33031/api/admin/strategies/false
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"parameters[0].name\" is not allowed to be empty."},{"message":"\"parameters[7].name\" is not allowed to be empty."},{"message":"\"parameters[8].name\" is not allowed to be empty."}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" length must be at least 2 characters long. You provided \"0\"."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"description": "A tag type for describing the color of a tag.", "icon": "not-really-used", "color": "#FFFFFF"}' http://0.0.0.0:33031/api/admin/tag-types/0
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - icon: Incorrect type
Response200 OK
<EMPTY>
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"description": "A tag type for describing the color of a tag.", "icon": null, "color": "#FFFFFF"}' http://0.0.0.0:33031/api/admin/tag-types/color
{"name":"UnknownError","message":"Empty .update() call detected! Update data does not contain any values to update. This will result in a faulty query. Table: tag_types. Columns: description,icon,color.","details":[{"message":"Empty .update() call detected! Update data does not contain any values to update. This will result in a faulty query. Table: tag_types. Columns: description,icon,color."}]}
{"name":"UnknownError","message":"update \"users\" set \"name\" = $1, \"email\" = $2 where \"deleted_at\" is null and \"is_service\" = $3 and \"is_system\" = $4 and \"id\" = $5 - duplicate key value violates unique constraint \"users_email_key\"","details":[{"message":"update \"users\" set \"name\" = $1, \"email\" = $2 where \"deleted_at\" is null and \"is_service\" = $3 and \"is_system\" = $4 and \"id\" = $5 - duplicate key value violates unique constraint \"users_email_key\""}]}
{"id":"c2afa882-310a-42d1-8b0a-7714462ed13b","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin/3
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - rootRole: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Could not find rootRole=Reader","details":[{"message":"Could not find rootRole=Reader"}]}
{"id":"c62a8ee4-3d0b-4961-a876-88941f74fef5","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/context/0
{"id":"175fa25b-f948-4f1b-960a-d6aee3afd50b","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/project` property must be string. You sent {}.","path":"/body/project"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 5 additional properties not defined in the schema (` `Ã`, `¤4.lß`, `Ñ2Ë
´øz璉#Ì` and 2 more). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"legalValues[4].value\" is not allowed to be empty."}]}
{"id":"60b622fa-ae60-471b-a8c5-d35c38688157","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/features-batch/export
{"id":"bbb09a4a-8348-4572-bd92-29b8d5909891","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"/body/features","message":"The `/body/features` property is required. It was not present on the data you sent."},{"path":"/body/tag","message":"The `/body/tag` property is required. It was not present on the data you sent."},{"message":"The `/body/project` property must be string. You // Output truncated...
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - project: Incorrect type
{"id":"74eb4cb8-bfbc-4ad6-98c8-5133895e42d5","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/features-batch/validate
{"id":"3f187767-2bf0-4c50-b3d6-00eae5a3a326","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/data/links/0/links/0/title` property must be string. You sent {}.","path":"/body/data/links/0/links/0/title"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - data -> links -> Array with invalid items: links -> Array with invalid items: title: Incorrect type
Response200 OK
{"errors":[{"message":"We detected the following segments that need to be created first:","affectedItems":["new-segment-name"]}],"warnings":[],"permissions":[]}
{"name":"UnknownError","message":"SELECT EXISTS (SELECT 1 FROM feature_strategies WHERE environment = $1 and feature_name in ($2,$3)) AS present - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"SELECT EXISTS (SELECT 1 FROM feature_strategies WHERE environment = $1 and feature_name in ($2,$3)) AS present - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Missing feedbackId","details":[{"message":"Missing feedbackId"}]}
Additional properties are not allowed ('createdAt', 'updatedAt', 'createdBy', 'project', 'environment' were unexpected)
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema:
{
"additionalProperties": false,
"type": "object",
"description": "Data about an application that's connected to Unleash via...
"required": [
"appName"
],
"properties": {
"appName": {
"description": "Name of the application",
"type": "string",
"example": "accounting"
},
"sdkVersion": {
"description": "Which SDK and version the application reporting u...
"type": "string",
"example": "unleash-client-java:8.0.0"
},
"strategies": {
// Output truncated...
}
Value:
{
"appName": "0",
"color": "red",
"createdAt": "2026-10-19T21:09:09.355Z",
"createdBy": null,
"description": null,
"environment": "development",
"icon": "https://github.com/favicon.ico",
"project": "projectA",
"strategies": [
"standard",
"gradualRollout",
"mySpecialCustomStrategy"
],
"updatedAt": "2026-10-19T21:09:26.772Z",
"url": "https://github.com/Unleash/unleash-proxy-client-js",
"usage": [
{
"environments": [
// Output truncated...
}
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/color:
{
"type": "string",
"description": "The CSS color that is used to color the application's ent...
"example": "red"
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/description:
{
"type": "string",
"description": "Extra information added about the application reporting t...
"example": "Application for reporting page visits"
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/icon:
{
"type": "string",
"description": "An URL to an icon file to be used for the applications's ...
"example": "https://github.com/favicon.ico"
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/url:
{
"type": "string",
"description": "A link to reference the application reporting the metrics...
"example": "https://github.com/Unleash/unleash-proxy-client-js"
}
Value:
null
{"id":"08a76d00-11ba-4c3d-8940-50e248321332","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/metrics/applications/0
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - icon: Incorrect type
{"id":"f43284e1-4225-42dc-9849-0d38cbc646fb","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/playground
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - context -> userId: Incorrect type
Response200 OK
{"input":{"environment":"development","projects":[],"context":{"appName":"My cool application.","currentTime":"2022-07-05T12:56:41+02:00","environment":"","properties":{"customContextField":"this is one!","otherCustomField":"3"},"remoteAddress":"192.168.1.1","sessionId":"b65e7b23-fec0-4814-a129-0e9861ef18fc","userId":""}},"features":[]}
{"name":"UnknownError","message":"select \"features\".\"name\" as \"name\", \"features\".\"description\" as \"description\", \"features\".\"type\" as \"type\", \"features\".\"project\" as \"project\", \"features\".\"stale\" as \"stale\", \"features\".\"impression_data\" as \"impression_data\", \"features\".\"created_at\" as \"created_at\", \"fe\".\"variants\" as \"variants\", \"fe\".\"enabled\" as \"enabled\", \"fe\".\"environment\" as \"environment\", \"fs\".\"id\" as \"strategy_id\", \"fs\".\"strategy_nam // Output truncated...
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - features -> Array with invalid items: Incorrect type
{"name":"UnknownError","message":"select * from \"features\" where \"name\" in ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10) order by \"name\" asc - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"select * from \"features\" where \"name\" in ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10) order by \"name\" asc - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - features -> Array with invalid items: Incorrect type
{"name":"UnknownError","message":"SELECT EXISTS (SELECT 1 FROM feature_environments WHERE feature_name = $1 AND environment = $2) AS present - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"SELECT EXISTS (SELECT 1 FROM feature_environments WHERE feature_name = $1 AND environment = $2) AS present - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 4 additional properties not defined in the schema (`>.`, `Q`, `Þ` and 1 more). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"ArchivedFeatureError","message":"Cannot perform this operation on archived features","details":[{"message":"Cannot perform this operation on archived features"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - features -> Array with invalid items: Incorrect type
{"id":"18371cdf-ffb2-4462-ac91-15986fe4d455","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/environments
{"id":"e51d9d2c-355f-4b73-99b8-74d485637c11","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/defaultStrategy/segments/0` property must be number. You sent {}.","path":"/body/defaultStrategy/segments/0"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Environment timeline does not exist","details":[{"message":"Environment timeline does not exist"}]}
{"name":"UnknownError","message":"SELECT EXISTS (SELECT 1 FROM environments WHERE name = $1) AS present - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"SELECT EXISTS (SELECT 1 FROM environments WHERE name = $1) AS present - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
{"id":"77bc68c4-b77d-4943-9023-8be833199b36","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/0/dependencies
{"id":"f29026c8-c1bd-43f9-99c8-d3170ede220c","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/variants/0` property must be string. You sent {}.","path":"/body/variants/0"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - feature: Incorrect type
{"id":"be241bee-2d12-487c-957b-c3f5b131b508","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"/body/name","message":"The `/body/name` property is required. It was not present on the data you sent."}]}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/checkout/clone
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" is not allowed to be empty."}]}
{"id":"9b6874c5-ceba-4d99-ab96-cd1cfabfe0d4","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/0/features/checkout/environments/0/strategies
{"id":"8d4f5ecc-23d3-4390-b78b-960c9082bf14","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/segments/0` property must be number. You sent {}.","path":"/body/segments/0"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Could not find strategy type with name ","details":[{"message":"Could not find strategy type with name "}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 5 additional properties not defined in the schema (``, ` `, `6` and 2 more). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Could not find strategy type with name eu-users","details":[{"message":"Could not find strategy type with name eu-users"}]}
{"name":"UnknownError","message":"select \"segments\".\"id\", \"segments\".\"name\", \"segments\".\"description\", \"segments\".\"segment_project_id\", \"segments\".\"created_by\", \"segments\".\"created_at\", \"segments\".\"constraints\" from \"segments\" where \"id\" = $1 - value \"-7634050440834865\" is out of range for type integer","details":[{"message":"select \"segments\".\"id\", \"segments\".\"name\", \"segments\".\"description\", \"segments\".\"segment_project_id\", \"segments\".\"created_by\", \"s // Output truncated...
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: No environments provided","details":[{"message":"No environments provided"}]}
{"id":"df71931e-7d96-4d9c-b1d5-935906177fcb","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/checkout/variants-batch
{"name":"UnknownError","message":"SELECT EXISTS(SELECT 1\n FROM change_request_settings\n WHERE environment = $1\n and project = $2) AS present - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"SELECT EXISTS(SELECT 1\n FROM change_request_settings\n WHERE environment = $1\n and project = $2) AS present - invalid byte sequenc // Output truncated...
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - features -> Array with invalid items: Incorrect type
{"name":"NotFoundError","message":"Active project with id Ør\u001c¼L\u0019Ö³ does not exist","details":[{"message":"Active project with id Ør\u001c¼L\u0019Ö³ does not exist"}]}
{"name":"UnknownError","message":"select * from \"features\" where \"name\" in ($1, $2, $3, $4) order by \"name\" asc - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"select * from \"features\" where \"name\" in ($1, $2, $3, $4) order by \"name\" asc - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
{"id":"9e76b2fd-d06f-4d5d-aa90-a27ecbb8c9b9","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/stale` property must be boolean. You sent {}.","path":"/body/stale"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - stale: Incorrect type
{"name":"UnknownError","message":"select * from \"features\" where \"name\" in ($1, $2, $3, $4, $5) order by \"name\" asc - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"select * from \"features\" where \"name\" in ($1, $2, $3, $4, $5) order by \"name\" asc - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
{"id":"a18ece33-7e32-4400-82b0-5fe7b1374dcc","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/query/type` property must match pattern \"^(IS|IS_ANY_OF):(.*?)(,([a-zA-Z0-9_]+))*$\". You sent \"\".","path":"/query/type"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/search/events?type='
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"id":"5d5c5bb6-146f-4004-89c9-e77a9adb6182","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/query/groupId` property must match pattern \"^(IS|IS_ANY_OF):(.*?)(,([0-9]+))*$\". You sent \"IS:G\\r,6,8300588021,5261,8612\".","path":"/query/groupId"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/search/events?from=IS%3A7625-07-03&groupId=IS%3AG%0D%F1%82%A3%A3%2C6%2C8300588021%2C5261%2C8612&offset=50&limit=50'
{"id":"989ba02b-a2ff-46a6-b7c2-ee3cd17feb31","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/query/status` property must be array. You sent \"production:enabled\".","path":"/query/status"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/search/features?query=feature_a&project=IS%3Adefault&state=IS%3Aactive&lifecycle=IS%3Ainitial&type=IS%3Arelease&createdBy=IS%3A1&tag=INCLUDE%3Asimple%3Amy_tag&segment=INCLUDE%3Apro-users&offset=50&limit=50&sortBy=type&sortOrder=desc&favoritesFirst=true&archived=IS%3Atrue&favorite=IS%3Atrue&createdAt=IS_ON_OR_AFTER%3A2023-01-28&lastSeenAt=IS_ON_OR_AFTER%3A2023-01-28&status=production%3Aenabled'
{"name":"UnknownError","message":"with \"ranked_features\" as (select \"features\".\"name\" as \"feature_name\", \"features\".\"description\" as \"description\", \"features\".\"type\" as \"type\", \"features\".\"archived_at\" as \"archived_at\", \"features\".\"project\" as \"project\", \"features\".\"created_at\" as \"created_at\", \"features\".\"stale\" as \"stale\", \"features\".\"impression_data\" as \"impression_data\", \"feature_environments\".\"enabled\" as \"enabled\", \"feature_environments\".\"envi // Output truncated...
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/search/features?lastSeenAt=IS_BEFORE%3A0202-79-03&limit=50&sortOrder=desc&favorite=IS%3Atrue'
{"name":"UnknownError","message":"Undefined binding(s) detected when compiling FIRST. Undefined column(s): [id] query: select \"password_hash\" from \"users\" where \"deleted_at\" is null and \"is_service\" = ? and \"is_system\" = ? and \"id\" = ? limit ?","details":[{"message":"Undefined binding(s) detected when compiling FIRST. Undefined column(s): [id] query: select \"password_hash\" from \"users\" where \"deleted_at\" is null and \"is_service\" = ? and \"is_system\" = ? and \"id\" = ? limit ?"}]}
{"id":"fb4e0f85-8c41-4af9-b70c-3c899b9f2afb","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user/change-password
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - tokens -> Array with invalid items: Incorrect type
Response200 OK
{"tokens":[]}
Reproduce
curl -X POST -H 'Content-Type: application/json' -d '{"tokens": [null]}' http://0.0.0.0:33031/edge/validate
{"name":"UnknownError","message":"select count(*) from \"events\" where \"project\" in ($1) limit $2 - invalid byte sequence for encoding \"UTF8\": 0x00","details":[{"message":"select count(*) from \"events\" where \"project\" in ($1) limit $2 - invalid byte sequence for encoding \"UTF8\": 0x00"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/events?project=%00%C2%AC%C3%A4u%C2%B1%C2%BB%C3%AE%F3%81%B5%A1%C2%90%F3%90%8B%89%C2%81%F1%A2%A5%BF%F3%BD%95%86%13'
{"name":"NotFoundError","message":"Could not find context field region in project default","details":[{"message":"Could not find context field region in project default"}]}
{"id":"ba741bea-c895-494b-8e5d-8b2983e62c29","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/context/0
{"id":"8721c18d-c4f9-44d9-a9eb-4ae14db59ecc","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/project` property must be string. You sent {}.","path":"/body/project"}]}
{"id":"997d33a6-e985-48a4-982e-ec837e3b00b7","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"null,null\".","path":"/params/id"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/segments/null%2Cnull
{"name":"UnknownError","message":"select \"segments\".\"id\", \"segments\".\"name\", \"segments\".\"description\", \"segments\".\"segment_project_id\", \"segments\".\"created_by\", \"segments\".\"created_at\", \"segments\".\"constraints\" from \"segments\" where \"id\" = $1 - value \"18638966323\" is out of range for type integer","details":[{"message":"select \"segments\".\"id\", \"segments\".\"name\", \"segments\".\"description\", \"segments\".\"segment_project_id\", \"segments\".\"created_by\", \"segment // Output truncated...
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/segments/18638966323
{"id":"bb8d5f2b-f51a-428d-baab-a44bd764ae7e","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"null,null\".","path":"/params/id"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/segments/null%2Cnull/strategies
{"name":"UnknownError","message":"select \"segments\".\"id\", \"segments\".\"name\", \"segments\".\"description\", \"segments\".\"segment_project_id\", \"segments\".\"created_by\", \"segments\".\"created_at\", \"segments\".\"constraints\" from \"segments\" where \"id\" = $1 - value \"437213995823\" is out of range for type integer","details":[{"message":"select \"segments\".\"id\", \"segments\".\"name\", \"segments\".\"description\", \"segments\".\"segment_project_id\", \"segments\".\"created_by\", \"segmen // Output truncated...
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/segments/437213995823/strategies
{"id":"6f4c5909-1904-4cdd-b93e-c3b3353e4aba","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"null,null\".","path":"/params/id"}]}
{"name":"UnknownError","message":"select * from \"users\" where \"deleted_at\" is null and \"is_service\" = $1 and \"is_system\" = $2 and \"id\" = $3 limit $4 - value \"-35184372088832\" is out of range for type integer","details":[{"message":"select * from \"users\" where \"deleted_at\" is null and \"is_service\" = $1 and \"is_system\" = $2 and \"id\" = $3 limit $4 - value \"-35184372088832\" is out of range for type integer"}]}
{"name":"UnknownError","message":"select * from \"users\" where \"deleted_at\" is null and \"is_service\" = $1 and \"is_system\" = $2 and \"id\" = $3 limit $4 - value \"6909027438\" is out of range for type integer","details":[{"message":"select * from \"users\" where \"deleted_at\" is null and \"is_service\" = $1 and \"is_system\" = $2 and \"id\" = $3 limit $4 - value \"6909027438\" is out of range for type integer"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin/6909027438
{"id":"bf1e070a-22d8-427b-868b-bcb40be42647","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"null,null\".","path":"/params/id"}]}
{"name":"UnknownError","message":"delete from \"personal_access_tokens\" where \"id\" = $1 and \"user_id\" = $2 returning \"id\", \"description\", \"user_id\", \"expires_at\", \"created_at\", \"seen_at\", \"selector\" - value \"16836729059244\" is out of range for type integer","details":[{"message":"delete from \"personal_access_tokens\" where \"id\" = $1 and \"user_id\" = $2 returning \"id\", \"description\", \"user_id\", \"expires_at\", \"created_at\", \"seen_at\", \"selector\" - value \"16836729059244\" // Output truncated...
{"name":"UnknownError","message":"Can only find users with id, username or email.","details":[{"message":"Can only find users with id, username or email."}]}
{"id":"ef127172-ec77-42a0-a3b1-03aa805066b4","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"/body/email","message":"The `/body/email` property is required. It was not present on the data you sent."}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"OwaspValidationError","message":"The password must be at least 10 characters long.","details":[{"validationErrors":["The password must be at least 10 characters long.","The password must contain at least one uppercase letter.","The password must contain at least one special character."],"message":"The password must be at least 10 characters long."}]}
{"id":"0a62be5a-e48c-4765-a692-236b6a67e9a4","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/api-tokens
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - tokenName: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Environment=default does not exist","details":[{"message":"Environment=default does not exist"}]}
Response header does not conform to the schema+3 moreless
Schema-valid request rejected
Schema-violating request accepted
Undocumented status code
1,034
Response header does not conform to the schemaST108
"strategies/my-custom-strategy" is not a "uri"
Schema:
{
"format": "uri",
"type": "string"
}
Value:
"strategies/my-custom-strategy"
Response201 Created
{"displayName":null,"name":"my-custom-strategy","editable":true,"description":"Enable the feature for users who have not logged in before.","parameters":[{"name":"Rollout percentage","type":"percentage","description":"How many percent of users should see this feature?","required":false}],"deprecated":false,"title":"My awesome strategy"}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"name": "my-custom-strategy", "title": "My awesome strategy", "description": "Enable the feature for users who have not logged in before.", "editable": false, "deprecated": true, "parameters": [{"name": "Rollout percentage", "type": "percentage", "description": "How many percent of users should see this feature?", "required": false}]}' http://0.0.0.0:33031/api/admin/strategies
{"id":"7fbe88b6-edb3-43af-9e68-12d2a4360c12","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/parameters/0/required` property must be boolean. You sent {}.","path":"/body/parameters/0/required"}]}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"name": "my-custom-strategy", "title": "My awesome strategy", "description": "Enable the feature for users who have not logged in before.", "editable": false, "deprecated": true, "parameters": [{"name": "Rollout percentage", "type": "percentage", "description": "How many percent of users should see this feature?", "required": {}}]}' http://0.0.0.0:33031/api/admin/strategies
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
Response201 Created
{"displayName":null,"name":"false","editable":true,"description":"Enable the feature for users who have not logged in before.","parameters":[],"deprecated":false,"title":"My awesome strategy"}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"name": false, "title": "My awesome strategy", "description": "Enable the feature for users who have not logged in before.", "editable": false, "deprecated": true, "parameters": []}' http://0.0.0.0:33031/api/admin/strategies
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" must be URL friendly. You provided \"fªû\"."}]}
{"id":"e65cc770-e1d7-47e4-b040-418057b98c38","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/invite-link/tokens
Response header does not conform to the schemaST108
"tokens/5ed821a35ee48405b0b1fb8d7002886a" is not a "uri"
Schema:
{
"format": "uri",
"type": "string"
}
Value:
"tokens/5ed821a35ee48405b0b1fb8d7002886a"
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
Response header does not conform to the schema+2 moreless
Schema-valid request rejected
Schema-violating request accepted
1,021
Response header does not conform to the schemaST108
"tag-types/color" is not a "uri"
Schema:
{
"format": "uri",
"type": "string"
}
Value:
"tag-types/color"
Response201 Created
{"name":"color","description":"A tag type for describing the color of a tag.","icon":"not-really-used","color":"#FFFFFF"}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"name": "color", "description": "A tag type for describing the color of a tag.", "icon": "not-really-used", "color": "#FFFFFF"}' http://0.0.0.0:33031/api/admin/tag-types
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
Response201 Created
{"color":"#000000","description":"A tag type for describing the color of a tag.","icon":null,"name":"false"}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"color": "#000000", "description": "A tag type for describing the color of a tag.", "icon": null, "name": false}' http://0.0.0.0:33031/api/admin/tag-types
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" must be URL friendly. You provided \";\"."}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: User already exists","details":[{"message":"User already exists"}]}
{"id":"3ffdc754-5761-407f-a15e-dda45cac88c6","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin
"name" is a required property
Validated against the response schema for status code 200.
Schema:
{
"required": [
"name"
],
"type": "object",
"additionalProperties": false,
"description": "A tag type.",
"properties": {
"name": {
"type": "string",
"description": "The name of the tag type.",
"example": "color"
},
"description": {
"type": "string",
"description": "The description of the tag type.",
"example": "A tag type for describing the color of a tag."
},
"icon": {
// Output truncated...
}
Value:
{
"tagType": {
"color": "#FFFFFF",
"description": "A tag type for describing the color of a tag.",
"icon": "not-really-used",
"name": "color"
},
"version": 1
}
Additional properties are not allowed ('version', 'tagType' were unexpected)
Validated against the response schema for status code 200.
Schema:
{
"additionalProperties": false,
"type": "object",
"description": "A tag type.",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The name of the tag type.",
"example": "color"
},
"description": {
"type": "string",
"description": "The description of the tag type.",
"example": "A tag type for describing the color of a tag."
},
"icon": {
// Output truncated...
}
Value:
{
"tagType": {
"color": "#FFFFFF",
"description": "A tag type for describing the color of a tag.",
"icon": "not-really-used",
"name": "color"
},
"version": 1
}
Response200 OK
{"version":1,"tagType":{"name":"color","description":"A tag type for describing the color of a tag.","icon":"not-really-used","color":"#FFFFFF"}}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/tag-types/color
Additional properties are not allowed ('createdAt', 'instances', 'seenToggles', 'links' were unexpected)
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema:
{
"additionalProperties": false,
"type": "object",
"description": "Data about an application that's connected to Unleash via...
"required": [
"appName"
],
"properties": {
"appName": {
"description": "Name of the application",
"type": "string",
"example": "accounting"
},
"sdkVersion": {
"description": "Which SDK and version the application reporting u...
"type": "string",
"example": "unleash-client-java:8.0.0"
},
"strategies": {
// Output truncated...
}
Value:
{
"appName": "0",
"color": "red",
"createdAt": "2026-10-19T21:09:09.355Z",
"description": null,
"icon": "https://github.com/favicon.ico",
"instances": [
{
"appName": "0",
"clientIp": "::ffff:172.19.0.1",
"createdAt": "2026-10-19T21:09:26.801Z",
"environment": "development",
"instanceId": "application-name-dacb1234",
"lastSeen": "2026-10-19T21:09:26.801Z",
"sdkType": "backend",
"sdkVersion": "unleash-client-java:8.0.0"
},
{
"appName": "0",
// Output truncated...
}
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/description:
{
"type": "string",
"description": "Extra information added about the application reporting t...
"example": "Application for reporting page visits"
}
Value:
null
{"name":"standard","notFound":true} is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/strategies/items:
{
"type": "string"
}
Value:
{
"name": "standard",
"notFound": true
}
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/icon:
{
"type": "string",
"description": "An URL to an icon file to be used for the applications's ...
"example": "https://github.com/favicon.ico"
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/url:
{
"type": "string",
"description": "A link to reference the application reporting the metrics...
"example": "https://github.com/Unleash/unleash-proxy-client-js"
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/applicationSchema/properties/color:
{
"type": "string",
"description": "The CSS color that is used to color the application's ent...
"example": "red"
}
Value:
null
null is not of type "boolean"
Validated against the response schema for status code 200.
Schema at /components/schemas/featureEnvironmentSchema/properties/enabled:
{
"type": "boolean",
"example": true,
"description": "`true` if the feature is enabled for the environment, oth...
}
Value:
null
null is not of type "number"
Validated against the response schema for status code 200.
Schema at /components/schemas/featureEnvironmentSchema/properties/sortOrder:
{
"type": "number",
"example": 3,
"description": "The sort order of the feature environment in the feature ...
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/featureEnvironmentSchema/properties/name:
{
"type": "string",
"example": "my-dev-env",
"description": "The name of the environment"
}
Value:
null
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/featureEnvironmentSchema/properties/type:
{
"type": "string",
"example": "development",
"description": "The type of the environment"
}
Value:
null
"userId" is a required property
Validated against the response schema for status code 200.
Schema:
{
"required": [
"userId",
"splashId",
"seen"
],
"type": "object",
"description": "Data related to a user having seen a splash screen.",
"properties": {
"userId": {
"type": "integer",
"description": "The ID of the user that was shown the splash scre...
"example": 1
},
"splashId": {
"type": "string",
"description": "The ID of the splash screen that was shown.",
"example": "new-splash-screen"
},
// Output truncated...
}
Value:
{
"seen": true,
"splashId": "0"
}
Response200 OK
{"splashId":"0","seen":true}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/splash/0
null is not of type "string"
Validated against the response schema for status code 200.
Schema at /components/schemas/tagTypeSchema/properties/description:
{
"type": "string",
"description": "The description of the tag type.",
"example": "A tag type for describing the color of a tag."
}
Value:
null
Response200 OK
{"version":1,"tagTypes":[{"name":"simple","description":"Used to simplify filtering of features","icon":"#","color":"#FFFFFF"},{"name":"team","description":"Seeded","icon":null,"color":null},{"name":"color","description":"A tag type for describing the color of a tag.","icon":"not-really-used","color":"#FFFFFF"},{"name":"my-custom-strategy","description":null,"icon":null,"color":null},{"name":"eu-users","description":null,"icon":null,"color":null},{"name":"environment","description":null,"icon":null,"color": // Output truncated...
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/tag-types
{"id":"33d9c116-1890-4b65-a3f9-b7210e796af5","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:development.workbenchclient000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/client/metrics
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - bucket -> toggles -> Object with invalid additional property: variants -> Object with invalid additional property: Incorrect type
{"id":"c54edbcb-df41-4593-be78-eff8c50da86e","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/invite-link/tokens/0
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - seenTokens -> Array with invalid items: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"id":"f0b0cd5f-ebc5-4554-8644-91d2966cd343","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `type` property must be equal to one of the allowed values: \"counter\", \"gauge\". You provided \"histogram\", which is not valid. Please use one of the allowed values instead..","path":"type"},{"message":"The \"/body/impactMetrics/0/samples/0/labels/x-schemathesis-additional\" // Output truncated...
{"id":"a4f1f81d-bf43-4ee0-b54c-2d224b718710","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/invite/0/signup
{"id":"f0d94790-def8-4889-83aa-323a1c6363ec","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/context/validate
{"id":"567f112b-79b0-4620-afa3-aced0584cbbc","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/name` property must be string. You sent {}.","path":"/body/name"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - name: Incorrect type
{"name":"NameExistsError","message":"A context field with that name already exist","details":[{"message":"A context field with that name already exist"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" is not allowed to be empty."}]}
{"id":"bb460f5e-b8b9-4fd0-8171-0ef67e6e5eb8","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/context/0/legal-values
{"id":"ffdf4d66-929c-4587-88b3-0483320885f4","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/description` property must be string. You sent {}.","path":"/body/description"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"value\" is not allowed to be empty."}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body
- violates `type` at /properties/description (was string, became null)
- violates `type` at /properties/value (was string, became boolean)
{"id":"62ae29f2-2943-410f-b3f6-87ca1ce82a21","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/features/checkout/tags
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - removedTags -> Array with invalid items: type: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Tag type '0000000000000000000000000000000000000000000000000' does not exist","details":[{"message":"Tag type '0000000000000000000000000000000000000000000000000' does not exist"}]}
{"id":"64873768-388e-4e05-86eb-0add9057b794","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/context/validate
{"id":"f478a64f-bf4f-4fa6-8d5b-21779c02ead6","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/name` property must be string. You sent {}.","path":"/body/name"}]}
{"name":"NameExistsError","message":"A context field with that name already exist","details":[{"message":"A context field with that name already exist"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - violates `type` at /properties/name (was string, became integer)
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" must be URL friendly. You provided \"Y\"."}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"ArchivedFeatureError","message":"Cannot perform this operation on archived features","details":[{"message":"Cannot perform this operation on archived features"}]}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/checkout/environments/production/off
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"ArchivedFeatureError","message":"Cannot perform this operation on archived features","details":[{"message":"Cannot perform this operation on archived features"}]}
Reproduce
GET/api/admin/projects
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/projects?archived=true'
POST/api/admin/projects/default/features/checkout/environments/production/onfailed here
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/checkout/environments/production/on
{"id":"0340e791-3ce0-4407-8f37-4fed7ee3c247","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:development.workbenchclient000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/client/register
{"id":"d721ce25-271d-4ccc-9d1b-4fdfdbb89b4e","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/strategies/0` property must be string. You sent {}.","path":"/body/strategies/0"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - strategies -> Array with invalid items: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 1 additional property not defined in the schema (`Ûm?
m𐛐`). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"interval\" must be a safe number. You provided 51110568227999440."}]}
{"id":"d3da8235-7a0c-4f79-9a7c-951a63befbda","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:development.workbenchfrontend00000000000000000000000000000000000000000' http://0.0.0.0:33031/api/frontend/client/metrics
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - bucket -> toggles -> Object with invalid additional property: variants -> Object with invalid additional property: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"bucket.toggles.}Ú;.yes\" must be a safe number. You provided 2.299343707581809e+106."}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - value: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"values[0]\" is not allowed to be empty."}]}
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: You can't use an admin token to import features. Please use either a personal access token (https://docs.getunleash.io/concepts/api-tokens-and-client-keys#personal-access-tokens) or a service account (https://docs.getunleash.io/concepts/service-accounts).","details":[{"message":"You can't use an admin token to import features. Please use either a personal access token (https://docs.getunleash.io/co // Output truncated...
{"id":"201ce820-432c-4d7f-abf6-f3d7e2ad13f7","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/features-batch/import
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - projectId: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 1 additional property not defined in the schema (``). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" is not allowed to be empty."}]}
{"name":"NotFoundError","message":"Could not find context field region in project default","details":[{"message":"Could not find context field region in project default"}]}
{"id":"1946c3bf-0b0a-41b8-a942-f513cd97a740","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/context/0/legal-values
{"id":"2a97c9bd-aaca-4dcd-b2f1-a421aa273804","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/description` property must be string. You sent {}.","path":"/body/description"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - description: Incorrect type
{"id":"3e3e3e27-5fc3-4e12-b480-2b96ea7290e4","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
{"id":"4ffbb68b-fb6a-4ccd-9947-939486e85233","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/favorites
{"id":"33596759-72f9-425e-8308-0112aa8483f2","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/impressionData` property must be boolean. You sent {}.","path":"/body/impressionData"}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"description": "Controls disabling of the comments section in case of an incident", "type": "kill-switch", "stale": true, "archived": true, "impressionData": {}}' http://0.0.0.0:33031/api/admin/projects/default/features/checkout
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - impressionData: Incorrect type
Response200 OK
{"name":"checkout","description":"Controls disabling of the comments section in case of an incident","type":"kill-switch","project":"default","stale":true,"createdAt":"2026-10-19T21:09:07.620Z","impressionData":false,"archivedAt":"2026-10-19T21:09:34.669Z","archived":true}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"description": "Controls disabling of the comments section in case of an incident", "type": "kill-switch", "stale": true, "archived": true, "impressionData": null}' http://0.0.0.0:33031/api/admin/projects/default/features/checkout
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: trying to change strategies for environment via update sortOrder","details":[{"message":"trying to change strategies for environment via update sortOrder"}]}
{"id":"7ed1f5a2-eb10-4c35-bd9c-5f24ec16928b","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/0/features/checkout/environments/0/strategies/set-sort-order
{"name":"NotFoundError","message":"Feature checkout does not have environment 0","details":[{"message":"Feature checkout does not have environment 0"}]}
{"id":"9cff21c3-e356-4327-b127-0ec2d652600b","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Could not apply provided patch: Cannot read properties of undefined (reading 'length')","details":[{"message":"Could not apply provided patch: Cannot read properties of undefined (reading 'length')"}]}
{"id":"ff436122-20c0-4074-842b-2c7d081249dd","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
{"id":"e527ae5a-06c8-4c58-aa3a-9c7185c8dd1b","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/checkout/favorites
{"id":"499651f4-99ad-4cf2-9b0d-33eb8da18286","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"path":"/body/status","message":"The `/body/status` property is required. It was not present on the data you sent."}]}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/default/features/checkout/lifecycle/complete
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - statusValue: Incorrect type
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 1 additional property not defined in the schema (`ª`). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Invalid URL: ~±êº","details":[{"message":"Invalid URL: ~±êº"}]}
{"id":"1306d4c8-09d4-4b69-8bae-401dd38a0f6b","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/record-ui-error
{"id":"a1e9b3c5-c8be-4478-a8ef-b7bbefffd487","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/errorStack` property must be string. You sent {}.","path":"/body/errorStack"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - errorStack: Incorrect type
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - violates `type` at /properties/name (was string, became boolean)
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Segment name cannot be empty","details":[{"message":"Segment name cannot be empty"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"\"name\" length must be at least 2 characters long. You provided \"P\"."}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body
- violates `anyOf` at /properties/icon
- violates `type` at /properties/name (was string, became integer)
{"id":"de8dcc92-90b2-45a5-a263-87ba7daf21eb","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/ui-config/cors
{"id":"7277fb9c-7773-49fd-894a-b2435f4fd44a","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/frontendApiOrigins/0` property must be string. You sent {}.","path":"/body/frontendApiOrigins/0"}]}
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: The expiry date should be in future.","details":[{"message":"The expiry date should be in future."}]}
{"id":"c8f0bb87-8229-41b1-a696-38b79889f463","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: user:bdc67c2831855419d860b436f467fe4aac38d28c9dcbc477551108c3' http://0.0.0.0:33031/api/admin/user/tokens
{"id":"6cc73758-b1ca-474a-9a68-ddd5959de783","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:development.workbenchfrontend00000000000000000000000000000000000000000' http://0.0.0.0:33031/api/frontend
{"id":"acc7717e-6af7-4ab9-9231-6410eef912d8","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/context/userId` property must be string. You sent {}.","path":"/body/context/userId"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - context -> userId: Incorrect type
{"id":"fb16c61f-c14c-4300-82f9-bd742b6d0179","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:development.workbenchfrontend00000000000000000000000000000000000000000' http://0.0.0.0:33031/api/frontend/client/register
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - strategies -> Array with invalid items: Incorrect type
{"name":"OwaspValidationError","message":"The password must contain at least one uppercase letter.","details":[{"validationErrors":["The password must contain at least one uppercase letter.","The password must contain at least one number."],"message":"The password must contain at least one uppercase letter."}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: A validation error occurred while processing your request data. Please make sure it conforms to the request data schema.","details":[{"message":"A validation error occurred while processing your request data. Please make sure it conforms to the request data schema."}]}
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"provider": "webhook", "description": "This addon posts updates to our internal feature tracking system whenever a feature is created or updated.", "parameters": {"url": "http://localhost:4242/webhook"}, "events": ["feature-created", "feature-updated"], "projects": ["new-landing-project", "signups-v2"], "environments": ["development", "production"], "enabled": false}' http://0.0.0.0:33031/api/admin/addons
{"id":"96274420-da89-45e9-a85c-30383570cd63","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/expiresAt` property must match format \"date-time\". You sent \"\".","path":"/body/expiresAt"}]}
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - lifetimeDays: Incorrect type
Response200 OK
{"id":"release","name":"Release","description":"Roll out new or incomplete features. Expected lifetime ~40 days","lifetimeDays":null}
{"id":"f9840cff-8daa-46b2-a09d-2cd871bdeb44","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/maintenance
{"id":"d8342399-18f7-4f99-9d56-294097b99151","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/query/archived` property must be boolean. You sent [\"null\",\"null\"].","path":"/query/archived"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/projects?archived=null&archived=null'
Invalid data should have been rejected
Expected: 400, 401, 403, 404, 405, 406, 409, 415, 422, 428, 429, 5xx
Invalid component: in body - features -> Array with invalid items: Incorrect type
{"id":"28fb90c0-45b9-4bda-8d3f-584ce4703efb","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/projects/0/features/0/environments/0/variants
{"name":"NotFoundError","message":"There's no feature named \"0\" in project \"0\", but there's a feature with that name in project \"default\"","details":[{"message":"There's no feature named \"0\" in project \"0\", but there's a feature with that name in project \"default\""}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Hint: The request body contains 5 additional properties not defined in the schema (``, `fB`, `sÃ[` and 2 more). The server appears to reject properties the schema allows. Declare `additionalProperties: false` if extras are not accepted, or make the server ignore unknown fields.
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: Invalid URL: \u0017","details":[{"message":"Invalid URL: \u0017"}]}
Valid data should have been accepted
Expected: 2xx, 3xx, 401, 403, 404, 409, 429, 5xx
Response400 Bad Request
{"name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data: User id is missing in request user object","details":[{"message":"User id is missing in request user object"}]}
Reproduce
curl -X GET -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user/profile
{"id":"8c47d2c3-6ae2-4468-a2e9-7ae978bbb9fa","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X POST -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/auth/simple/login
{"id":"f7549eac-d171-4150-888b-34e2020c76c9","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/body/password` property must be string. You sent {}.","path":"/body/password"}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"d57d6c33-665d-4a01-b2fc-1065ce7b95d2","name":"NotFoundError","message":"The path you were looking for (/api/admin/addons) is not available.","details":[{"message":"The path you were looking for (/api/admin/addons) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"provider": "webhook", "description": "This addon posts updates to our internal feature tracking system whenever a feature is created or updated.", "enabled": false, "parameters": {"url": "http://localhost:4242/webhook"}, "events": ["feature-created", "feature-updated"], "projects": ["new-landing-project", "signups-v2"], "environments": ["development", "production"]}' http://0.0.0.0:33031/api/admin/addons
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"cf55d2ae-e8fd-4866-a1ff-5c943a106471","name":"NotFoundError","message":"The path you were looking for (/api/admin/api-tokens) is not available.","details":[{"message":"The path you were looking for (/api/admin/api-tokens) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"9a654b30-07f0-425e-b8fd-a04a2d25ce15","name":"NotFoundError","message":"The path you were looking for (/api/admin/constraints/validate) is not available.","details":[{"message":"The path you were looking for (/api/admin/constraints/validate) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"06db221f-e96b-4bb5-b76a-273de7795a04","name":"NotFoundError","message":"The path you were looking for (/api/admin/context) is not available.","details":[{"message":"The path you were looking for (/api/admin/context) is not available."}]}
Unsupported method PATCH returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"e044dc30-6eec-488f-a010-3cbe55b0ef9e","name":"NotFoundError","message":"The path you were looking for (/api/admin/context/validate) is not available.","details":[{"message":"The path you were looking for (/api/admin/context/validate) is not available."}]}
`Allow: GET,HEAD,PUT,DELETE,POST` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"56c87639-5d52-465e-84a9-0190f929c83b","name":"NotFoundError","message":"The path you were looking for (/api/admin/features-batch/export) is not available.","details":[{"message":"The path you were looking for (/api/admin/features-batch/export) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"f16b5bbf-7230-402d-9587-9061deba8cef","name":"NotFoundError","message":"The path you were looking for (/api/admin/features-batch/import) is not available.","details":[{"message":"The path you were looking for (/api/admin/features-batch/import) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"5e450e42-95e5-4666-b00d-395faa05c8bf","name":"NotFoundError","message":"The path you were looking for (/api/admin/features-batch/validate) is not available.","details":[{"message":"The path you were looking for (/api/admin/features-batch/validate) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"9c1a557d-aa3c-447f-b0d0-d4b872313c54","name":"NotFoundError","message":"The path you were looking for (/api/admin/features/validate) is not available.","details":[{"message":"The path you were looking for (/api/admin/features/validate) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"5ed7d599-98c7-4238-8bcc-ddcb9e552f32","name":"NotFoundError","message":"The path you were looking for (/api/admin/feedback) is not available.","details":[{"message":"The path you were looking for (/api/admin/feedback) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"31941b63-eb37-4c36-a09f-d95d8d8eafb2","name":"NotFoundError","message":"The path you were looking for (/api/admin/invite-link/tokens) is not available.","details":[{"message":"The path you were looking for (/api/admin/invite-link/tokens) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"d8d8edd8-4eac-46cf-bd3e-b2993d0e9cc7","name":"NotFoundError","message":"The path you were looking for (/api/admin/maintenance) is not available.","details":[{"message":"The path you were looking for (/api/admin/maintenance) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"80fb1623-eeef-41c3-add8-ae95b5b4504e","name":"NotFoundError","message":"The path you were looking for (/api/admin/playground) is not available.","details":[{"message":"The path you were looking for (/api/admin/playground) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"1a0cc761-4ce5-4e9b-971f-103feca6ad1a","name":"NotFoundError","message":"The path you were looking for (/api/admin/playground/advanced) is not available.","details":[{"message":"The path you were looking for (/api/admin/playground/advanced) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"7876e10e-57cb-47f6-a52b-6beb0b7331e6","name":"NotFoundError","message":"The path you were looking for (/api/admin/record-ui-error) is not available.","details":[{"message":"The path you were looking for (/api/admin/record-ui-error) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"90b32069-6881-4f8f-b6a5-70d6a3e274b2","name":"NotFoundError","message":"The path you were looking for (/api/admin/segments) is not available.","details":[{"message":"The path you were looking for (/api/admin/segments) is not available."}]}
Unsupported method PUT returned 400, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response400 Bad Request
{"id":"1d450ce3-449b-4c34-a9e0-cf29d18b1f3b","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"validate\".","path":"/params/id"}]}
`Allow: POST,DELETE,PUT,GET,HEAD` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"ec034587-aa51-404d-9047-7a639e7e1775","name":"NotFoundError","message":"The path you were looking for (/api/admin/strategies) is not available.","details":[{"message":"The path you were looking for (/api/admin/strategies) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"name": "my-custom-strategy", "title": "My awesome strategy", "description": "Enable the feature for users who have not logged in before.", "editable": false, "deprecated": true, "parameters": []}' http://0.0.0.0:33031/api/admin/strategies
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"5d28788d-dd5e-4be5-86f1-1bcb5a174563","name":"NotFoundError","message":"The path you were looking for (/api/admin/tag-types) is not available.","details":[{"message":"The path you were looking for (/api/admin/tag-types) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"color": "#000000", "description": "A tag type for describing the color of a tag.", "icon": null, "name": "color"}' http://0.0.0.0:33031/api/admin/tag-types
Unsupported method PATCH returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"356e9d21-b842-4d03-87ff-6fe5b5081634","name":"NotFoundError","message":"The path you were looking for (/api/admin/tag-types/validate) is not available.","details":[{"message":"The path you were looking for (/api/admin/tag-types/validate) is not available."}]}
Reproduce
curl -X PATCH -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"color": "#000000", "description": "A tag type for describing the color of a tag.", "icon": null, "name": "color"}' http://0.0.0.0:33031/api/admin/tag-types/validate
`Allow: POST,GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
Response200 OK
POST,GET,HEAD,PUT,DELETE
Reproduce
curl -X OPTIONS -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' -H 'Content-Type: application/json' -d '{"color": "#000000", "description": "A tag type for describing the color of a tag.", "icon": null, "name": "color"}' http://0.0.0.0:33031/api/admin/tag-types/validate
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"e775aa07-124e-45cf-a5ff-a92996582852","name":"NotFoundError","message":"The path you were looking for (/api/admin/tags) is not available.","details":[{"message":"The path you were looking for (/api/admin/tags) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"505de382-668f-4bc3-8fd3-84474f695558","name":"NotFoundError","message":"The path you were looking for (/api/admin/ui-config/cors) is not available.","details":[{"message":"The path you were looking for (/api/admin/ui-config/cors) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"d19261d3-460b-4f4c-b1e7-713000c6d959","name":"NotFoundError","message":"The path you were looking for (/api/admin/user-admin) is not available.","details":[{"message":"The path you were looking for (/api/admin/user-admin) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"09d4ec54-f6f7-4375-890b-d8c6f5d748b1","name":"NotFoundError","message":"The path you were looking for (/api/admin/user-admin/inactive/delete) is not available.","details":[{"message":"The path you were looking for (/api/admin/user-admin/inactive/delete) is not available."}]}
Unsupported method PUT returned 400, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response400 Bad Request
{"id":"1cb8fd7b-c8de-4b01-a65b-9e89942a911e","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"reset-password\".","path":"/params/id"}]}
`Allow: POST,GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 400, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response400 Bad Request
{"id":"7f62870a-6025-4d24-bf50-095d4b5738ba","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"validate-password\".","path":"/params/id"}]}
`Allow: POST,GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"a0242054-c351-4193-9a4c-64f99785f18e","name":"NotFoundError","message":"The path you were looking for (/api/admin/user/change-password) is not available.","details":[{"message":"The path you were looking for (/api/admin/user/change-password) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"51167e0c-88f3-4152-bfd2-ea5884890b81","name":"NotFoundError","message":"The path you were looking for (/api/admin/user/tokens) is not available.","details":[{"message":"The path you were looking for (/api/admin/user/tokens) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"1f74957d-14ee-4f69-888b-15ac0437668e","name":"NotFoundError","message":"The path you were looking for (/api/client/metrics) is not available.","details":[{"message":"The path you were looking for (/api/client/metrics) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"44eba816-c390-425a-8c32-fd9c79738a90","name":"NotFoundError","message":"The path you were looking for (/api/client/metrics/bulk) is not available.","details":[{"message":"The path you were looking for (/api/client/metrics/bulk) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"f5f33f87-1c7f-4f10-8507-a08321d527cf","name":"NotFoundError","message":"The path you were looking for (/api/client/register) is not available.","details":[{"message":"The path you were looking for (/api/client/register) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"e06ac757-3db2-49ad-9fae-616ae35d8a5e","name":"NotFoundError","message":"The path you were looking for (/api/frontend) is not available.","details":[{"message":"The path you were looking for (/api/frontend) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"3baf6e3b-3862-48e0-99a0-b10d1c801588","name":"NotFoundError","message":"The path you were looking for (/api/frontend/client/metrics) is not available.","details":[{"message":"The path you were looking for (/api/frontend/client/metrics) is not available."}]}
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"5f232be5-bfa6-45ef-8006-767358b97f59","name":"NotFoundError","message":"The path you were looking for (/api/frontend/client/register) is not available.","details":[{"message":"The path you were looking for (/api/frontend/client/register) is not available."}]}
`Allow: GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: GET
List exactly the methods this resource supports in `Allow`
Unsupported method POST returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"28b2b952-ef5c-49f0-8b00-e402b143126c","name":"NotFoundError","message":"The path you were looking for (/api/admin/environments/sort-order) is not available.","details":[{"message":"The path you were looking for (/api/admin/environments/sort-order) is not available."}]}
`Allow: GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"8363429e-88d5-4851-acd1-42883517a6b7","name":"NotFoundError","message":"The path you were looking for (/api/admin/environments) is not available.","details":[{"message":"The path you were looking for (/api/admin/environments) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/environments
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"beb5c404-9db8-4020-ad5e-bec4be07dc30","name":"NotFoundError","message":"The path you were looking for (/api/admin/event-creators) is not available.","details":[{"message":"The path you were looking for (/api/admin/event-creators) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/event-creators
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"a2b06d9b-1724-4fce-a33e-945910b26b54","name":"NotFoundError","message":"The path you were looking for (/api/admin/events) is not available.","details":[{"message":"The path you were looking for (/api/admin/events) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/events?project='
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"2d0f68be-a81a-427c-8626-dba08d033652","name":"NotFoundError","message":"The path you were looking for (/api/admin/feature-types) is not available.","details":[{"message":"The path you were looking for (/api/admin/feature-types) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/feature-types
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"688f473e-58a0-4e6d-879e-4d7443a7b258","name":"NotFoundError","message":"The path you were looking for (/api/admin/instance-admin/statistics) is not available.","details":[{"message":"The path you were looking for (/api/admin/instance-admin/statistics) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/instance-admin/statistics
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"6581f938-51c3-463e-b0af-fd6557d44c5d","name":"NotFoundError","message":"The path you were looking for (/api/admin/instance-admin/statistics/csv) is not available.","details":[{"message":"The path you were looking for (/api/admin/instance-admin/statistics/csv) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/instance-admin/statistics/csv
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"ca0e6567-4494-4d3b-88c1-2d2c026e784a","name":"NotFoundError","message":"The path you were looking for (/api/admin/lifecycle/count) is not available.","details":[{"message":"The path you were looking for (/api/admin/lifecycle/count) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/lifecycle/count
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"ad2b7a4c-69dd-41d0-8137-33d07cf4bf8b","name":"NotFoundError","message":"The path you were looking for (/api/admin/metrics/applications) is not available.","details":[{"message":"The path you were looking for (/api/admin/metrics/applications) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/metrics/applications?query=first_app&offset=50&limit=50&sortBy=type&sortOrder=desc'
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"8fd90426-f5fa-4263-bc34-1e5187618e92","name":"NotFoundError","message":"The path you were looking for (/api/admin/metrics/sdks/outdated) is not available.","details":[{"message":"The path you were looking for (/api/admin/metrics/sdks/outdated) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/metrics/sdks/outdated
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"f85ade58-c2ab-44bb-938d-4bcf618d1e3a","name":"NotFoundError","message":"The path you were looking for (/api/admin/metrics/unknown-flags) is not available.","details":[{"message":"The path you were looking for (/api/admin/metrics/unknown-flags) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/metrics/unknown-flags
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"2f408a89-3e7b-45f7-8c43-27f2600c6822","name":"NotFoundError","message":"The path you were looking for (/api/admin/personal-dashboard) is not available.","details":[{"message":"The path you were looking for (/api/admin/personal-dashboard) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/personal-dashboard
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"036a10b7-84e7-4591-a82e-c02f06aa117d","name":"NotFoundError","message":"The path you were looking for (/api/admin/projects) is not available.","details":[{"message":"The path you were looking for (/api/admin/projects) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/projects?archived=true'
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"060e7f58-bba6-4c54-a257-0363992fce55","name":"NotFoundError","message":"The path you were looking for (/api/admin/telemetry/settings) is not available.","details":[{"message":"The path you were looking for (/api/admin/telemetry/settings) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/telemetry/settings
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"129459a5-cc42-4833-b438-1fc1f3d43332","name":"NotFoundError","message":"The path you were looking for (/api/admin/ui-config) is not available.","details":[{"message":"The path you were looking for (/api/admin/ui-config) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/ui-config
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"90ce15f4-6457-42ef-ae6e-b7644e8cea47","name":"NotFoundError","message":"The path you were looking for (/api/admin/user) is not available.","details":[{"message":"The path you were looking for (/api/admin/user) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user
Unsupported method PUT returned 415, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response415 Unsupported Media Type
{"id":"e8db8d38-c5fa-459a-b0db-dbc4b8f56b46","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin/access
`Allow: GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 415, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response415 Unsupported Media Type
{"id":"6d93a2f6-5567-4c08-a080-ad45f31367aa","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin/admin-count
`Allow: GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 415, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response415 Unsupported Media Type
{"id":"bdc53f91-4901-4306-9ad5-338f3e092a7d","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin/inactive
Unsupported method PUT returned 415, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response415 Unsupported Media Type
{"id":"69709ccc-c42b-419b-abba-a17451a74fc9","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/user-admin/search?q='
`Allow: GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: DELETE, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"715b0d0e-ac69-41e3-9d8e-978ec12ded8d","name":"NotFoundError","message":"The path you were looking for (/api/admin/user/profile) is not available.","details":[{"message":"The path you were looking for (/api/admin/user/profile) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user/profile
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"adb0e717-dc47-4e97-8b9d-649b250e39f7","name":"NotFoundError","message":"The path you were looking for (/api/admin/user/roles) is not available.","details":[{"message":"The path you were looking for (/api/admin/user/roles) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/user/roles?projectId=project-y'
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"1d7776ef-05b7-4ea0-8fc6-28e2c50ffbb3","name":"NotFoundError","message":"The path you were looking for (/api/client/features) is not available.","details":[{"message":"The path you were looking for (/api/client/features) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:development.workbenchclient000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/client/features
Unsupported method PUT returned 415, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response415 Unsupported Media Type
{"id":"556923b7-acdd-4683-8c9e-2f045ec1634b","name":"ContentTypeError","message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.","details":[{"message":"We do not accept the content-type you provided (you didn't provide one). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format." // Output truncated...
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' http://0.0.0.0:33031/api/admin/user-admin/scim-users
`Allow: GET,HEAD,PUT,DELETE` does not match the schema. Undocumented methods advertised: GET, PUT
List exactly the methods this resource supports in `Allow`
`Allow: GET,HEAD,PUT,DELETE,POST` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
Unsupported method PUT returned 404, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response404 Not Found
{"id":"3fab2a39-5527-4a91-af31-608f962b5b94","name":"NotFoundError","message":"The path you were looking for (/api/admin/search/events) is not available.","details":[{"message":"The path you were looking for (/api/admin/search/events) is not available."}]}
Reproduce
curl -X PUT -H 'Authorization: *:*.workbench0000000000000000000000000000000000000000000000' 'http://0.0.0.0:33031/api/admin/search/events?query=admin%40example.com&id=IS%3A123&groupId=IS%3A123&feature=IS%3Amyfeature&project=IS%3Adefault&type=IS%3Achange-added&createdBy=IS%3A2&from=IS%3A2024-01-01&to=IS%3A2024-01-31&offset=50&limit=50&environment=IS%3Aproduction'
Unsupported method PUT returned 400, expected 405 Method Not Allowed
Return 405 for methods not listed in the OpenAPI spec
Response400 Bad Request
{"id":"272b7f4a-27c7-4730-9f9e-885ef2ac3bb5","name":"BadDataError","message":"Request validation failed: your request body or params contain invalid data. Refer to the `details` list for more information.","details":[{"message":"The `/params/id` property must be integer. You sent \"strategies\".","path":"/params/id"}]}
`Allow: POST,DELETE,PUT,GET,HEAD` does not match the schema. Undocumented methods advertised: DELETE, GET, PUT
List exactly the methods this resource supports in `Allow`
`Allow: GET,HEAD,POST,PUT,PATCH,DELETE` does not match the schema. Undocumented methods advertised: DELETE, GET, PATCH, PUT
List exactly the methods this resource supports in `Allow`