additionalProperties API Origin: Application & API OSI layer 7 · Application Last updated 13 Oct 2026

API Error: Request failed schema validation (must NOT have additional properties / Additional properties are not allowed)

The JSON body doesn’t match the endpoint’s schema — an unknown property, wrong nesting, or a missing required object.

Exact message you may see must NOT have additional propertiesAdditional properties are not allowedmust have required propertywas unexpectedrequest.body should have required property
Seen on: REST API

Meaning

Many APIs validate bodies against a JSON Schema or OpenAPI definition. Ajv reports “must NOT have additional properties” or “must have required property 'x'”, Python jsonschema “Additional properties are not allowed ('x' was unexpected)”, OpenAPI validators “request.body should have required property”.

Strict schemas reject extra fields, so a typo in a field name or a field from a newer API version fails even though everything else is right.

Common causes

  • Unknown or misspelled property in the body
  • Object nested at the wrong level (flat vs wrapped in "data")
  • Required sub-object or array item missing
  • Sending a field that only exists in another API version

⚡ Quick fix

  1. Validate the payload against the published schema/OpenAPI file
  2. Remove fields the schema doesn’t define
  3. Check nesting against a docs example

Detailed fix by platform

Node.js

  1. javascript
    import Ajv from 'ajv';
    const validate = new Ajv({ allErrors: true }).compile(schema);
    if (!validate(body)) console.log(validate.errors);

Python

  1. python
    from jsonschema import validate
    validate(instance=payload, schema=schema)  # raises with the exact path

How to diagnose

  1. Path — Which instancePath / field does the error point to?
  2. Schema — additionalProperties, required, nesting
  3. Version — Is the schema for your API version?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

1005 — MySQL ERROR 1005 (HY000): Can't create table (errno: 150 "Foreign key constraint is incorrectly formed") (MySQL)10051007 — MySQL ERROR 1007 (HY000): Can't create database 'x'; database exists (MySQL)10071008 — MySQL ERROR 1008 (HY000): Can't drop database 'x'; database doesn't exist (MySQL)10081051 — MySQL ERROR 1051 (42S02): Unknown table 'x' (MySQL)10511054 — MySQL ERROR 1054 (42S22): Unknown column in 'field list' (MySQL)10541060 — MySQL ERROR 1060 (42S21): Duplicate column name 'x' (MySQL)10601067 — MySQL ERROR 1067 (42000): Invalid default value for 'created_at' (MySQL)10671075 — MySQL ERROR 1075 (42000): Incorrect table definition; there can be only one auto column and it must be defined as a key (MySQL)1075additiona…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.