Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions content/docs/protocol/kernel/error-handling.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -301,25 +301,30 @@ deriving it from this page.

#### `INVALID_FIELD`
**HTTP Status:** 400
**Meaning:** Field value has wrong type
**Meaning:** A field name in the request does not exist on the target object — a name that
resolves to nothing, not a value of the wrong type. On a list read it also covers an
unreserved query parameter, which `GET /data/:object` reads as a field filter.

**Example:**
```json
{
"success": false,
"error": {
"code": "INVALID_FIELD",
"message": "Field 'age' must be a number",
"message": "Unknown field 'age' on object 'contact'",
"details": {
"field": "age",
"expected_type": "number",
"actual_type": "string",
"value": "twenty-five"
"object": "contact"
}
}
}
```

The [error catalog's `INVALID_FIELD` entry](/docs/api/error-catalog#invalid_field) carries
the authoritative cause text — it enumerates every read axis this one code answers on
(`select`, `expand`, `searchFields`, `groupBy`, `aggregations[].field`) and the
off-request `backfillSummaryNulls` case.

### Resource Errors

#### `RESOURCE_NOT_FOUND`
Expand Down
Loading