A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-06 UTC."],[],["This document outlines various services within an ad management API, including AdRule, Adjustment, AdsTxt, AudienceSegment, and many others totaling over 40. It details the `ApiError` type, which includes `fieldPath`, `fieldPathElements`, `trigger`, and `errorString` fields. It also elaborates on `ParseError`, a specific error type with a `reason` field. `ParseError`'s reasons are `UNPARSABLE` or `UNKNOWN`, indicating parsing issues. The document lists the API's namespace and enumerations.\n"]]