Enum Values Validator

Overview

You send a JSON payload and, for each field you care about, the list of values it is allowed to hold. We look the field up by path and tell you when it holds something else, when it is null, or when it is not there at all. Where the value is a near-miss for one of your allowed values we name the one you probably meant, which turns a typo into a one-line fix. This is a targeted check on the fields you list, not full schema validation.

A single unexpected value in a status or currency field is enough to have an API reject your request, and writing the same membership check by hand in every caller is wasted effort. You describe the allowed values once and get a precise answer.

When to use it

Scope

Non-goals

• We never run full schema validation — that is schema.validate_json
• We never audit which fields are present overall — that is schema.check_required_fields
• We never change the payload or correct a value for you

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"schema.validate_enum_values","input":{"payload":{"status":"active"},"enums":[{"path":"/status","allowedValues":["active"]}]}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("schema.validate_enum_values", {"payload":{"status":"activ"},"enums":[{"allowedValues":["active","inactive"],"path":"/status"}]});

Errors

Other limits

Limitations

• We never run full schema validation — that is schema.validate_json
• We never audit which fields are present overall — that is schema.check_required_fields
• We never change the payload or correct a value for you
• Checking a whole document against a schema (schema.validate_json)
• Auditing which fields are present (schema.check_required_fields)
• Checking numeric ranges, lengths, or patterns

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "schema.validate_enum_values",
  "input": {
    "payload": {
      "status": "activ"
    },
    "enums": [
      {
        "allowedValues": [
          "active",
          "inactive"
        ],
        "path": "/status"
      }
    ]
  }
}

Examples

{
  "payload": {
    "status": "activ"
  },
  "enums": [
    {
      "allowedValues": [
        "active",
        "inactive"
      ],
      "path": "/status"
    }
  ]
}

{
  "errors": [
    {
      "suggestion": "active",
      "path": "/status",
      "actual": "activ",
      "allowedValues": [
        "active",
        "inactive"
      ]
    }
  ],
  "valid": false
}

{
  "payload": {
    "status": "active"
  },
  "enums": [
    {
      "allowedValues": [
        "active",
        "inactive"
      ],
      "path": "/status"
    }
  ]
}

{
  "errors": [],
  "valid": true
}

Recommended use cases

• Guard the status, type, and currency fields in a payload you are about to send
• Catch the case where an upstream service quietly added a new value you do not handle
• Turn a misspelled value into a concrete suggestion you can act on

Avoid for

• Checking a whole document against a schema (schema.validate_json)
• Auditing which fields are present (schema.check_required_fields)
• Checking numeric ranges, lengths, or patterns

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags