Postman API测试中JSON Schema验证失败问题求助

Hey there! I’ve run into similar JSON Schema validation headaches in Postman before, so let’s walk through how to fix this step by step. First, let’s use your sample response as a reference to ground our debugging.

First, Let’s Confirm a Correct Schema Template for Your Response #

Your response has a top-level object with an array comuni, which contains objects with specific string/number/boolean fields. Here’s a sample Schema that should align with your response structure:

{
  "type": "object",
  "properties": {
    "comuni": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "istat": { "type": "string" },
          "code": { "type": "string" },
          "comune": { "type": "string" },
          "provincia": { "type": "string" },
          "cap": { "type": "string" },
          "latitude": { "type": "number" },
          "longitude": { "type": "number" },
          "soppresso": { "type": "boolean" },
          "regione": { "type": "string" } // Adjust this based on the actual response value/type
        },
        // Only add fields that are ALWAYS present to the required array
        "required": ["istat", "code", "comune", "provincia", "cap", "latitude", "longitude", "soppresso"]
      }
    }
  },
  "required": ["comuni"]
}

Common Issues & Fixes #

• Mismatched Data Types
  This is the most frequent culprit. Double-check that each field’s type in your Schema matches the response exactly:

  • cap is a string ("20081") in your response—don’t incorrectly set it to "type": "number" in the Schema.
  • latitude/longitude are floats (not integers), so use "type": "number" (which covers both integers and floats).
  • soppresso is a boolean (false), so ensure your Schema doesn’t accidentally mark it as a string.

• Missing or Mismatched Required Fields
  If your Schema lists a field as required but the response doesn’t include it (like the truncated regione in your sample), validation will fail. Either:

  • Remove the field from the required array if it’s optional, or
  • Confirm the API actually returns that field in all cases.

• Ignoring Postman’s Error Details
  Don’t skip the error message in Postman’s Test Results tab! It will tell you exactly what’s wrong—for example:

  comuni[0].regione is required but not present
  comuni[0].cap should be number but is string
  These specific clues are gold for fixing the issue fast.

• Overly Strict Schema Rules
  If you’re using additional validation rules (like minimum for numbers, or pattern for strings), make sure they match the actual response values. For example, if you set a pattern for istat that expects 6 digits but the response has "015002" (which fits), that’s fine—but if your pattern expects 5 digits, it will fail.

Quick Debugging Trick #

Start with a super simplified Schema to narrow down the problem:

{
  "type": "object",
  "properties": {
    "comuni": { "type": "array" }
  }
}

If this passes, gradually add more field validations one by one. This will help you isolate exactly which field or rule is causing the failure.

内容的提问来源于stack exchange，提问作者mpeg90