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.
The format of the URL is not allowed. This could occur for a number of
reasons. For example, if an invalid scheme is specified (like "ftp://")
or if a port is specified when not required, or if a query was specified
when not required.
INSECURE_SCHEME
URL contains insecure scheme.
NO_SCHEME
The URL does not contain a scheme.
UNKNOWN
The value returned if the actual value is not exposed by the requested API version.
[[["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."],[[["\u003cp\u003eThe InvalidUrlError object identifies errors associated with URLs in the system.\u003c/p\u003e\n"],["\u003cp\u003eThis error is triggered when a URL contains invalid characters, has an incorrect format, or uses an insecure scheme.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ereason\u003c/code\u003e field provides more specific information about the cause of the error, such as \u003ccode\u003eILLEGAL_CHARACTERS\u003c/code\u003e or \u003ccode\u003eINVALID_FORMAT\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eInvalidUrlError inherits from ApiError, providing additional context with fields like \u003ccode\u003efieldPath\u003c/code\u003e, \u003ccode\u003etrigger\u003c/code\u003e, and \u003ccode\u003eerrorString\u003c/code\u003e.\u003c/p\u003e\n"]]],["The provided content details various services and their associated errors within a specific API framework (v202408). It lists services like Adjustment, Company, Content, Creative, and others, with links to their respective documentation. A hierarchy of errors is presented, starting from `ApiError` and branching into specific error types like `InvalidUrlError`, `AuthenticationError`, and `QuotaError`. The `InvalidUrlError` further specifies reasons for URL invalidity, including `ILLEGAL_CHARACTERS`, `INVALID_FORMAT`, and `NO_SCHEME`. Also the structure of `ApiError` is shown.\n"],null,[]]