type BillingError (v202411)
Stay organized with collections
Save and categorize content based on your preferences.
Lists all errors associated with the billing settings of a proposal or proposal line item.
- Namespace
-
https://www.google.com/apis/ads/publisher/v202411
Field
|
ApiError (inherited)
|
fieldPath
|
xsd:string
The OGNL field path to identify cause of error.
|
fieldPathElements
|
FieldPathElement[]
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.
|
BillingError
|
reason
|
BillingError.Reason
The error reason represented by an enum.
Enumerations
-
UNSUPPORTED_BILLING_SCHEDULE
- Found unsupported billing schedule.
-
UNSUPPORTED_BILLING_CAP
- Found unsupported billing cap.
-
MISSING_BILLING_SOURCE
- Billing source is missing when either billing scheule or billing cap is provided.
-
MISSING_BILLING_SCHEDULE
- Billing schedule is missing when the provided billing source is CONSTRACTED.
-
MISSING_BILLING_CAP
- Billing cap is missing when the provided billing source is not CONSTRACTED.
-
INVALID_BILLING_SOURCE_FOR_OFFLINE
- The billing source is invalid for offline proposal line item.
-
UPDATE_BILLING_NOT_ALLOWED
- Billing settings cannot be updated once the proposal has been approved.
-
MISSING_BILLING_BASE
- Billing base is missing when the provided billing source is CONTRACTED.
-
INVALID_BILLING_BASE
- The billing base is invalid for the provided billing source.
-
UNKNOWN
- The value returned if the actual value is not exposed by the requested API version.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-06 UTC.
[null,null,["Last updated 2025-08-06 UTC."],[[["\u003cp\u003eBillingError objects encompass issues related to billing settings within proposals and proposal line items.\u003c/p\u003e\n"],["\u003cp\u003eThese errors provide structured details including an error reason, a field path indicating the location of the error, and potential trigger data.\u003c/p\u003e\n"],["\u003cp\u003eCommon BillingError reasons include unsupported billing schedules or caps, missing billing information, and invalid billing sources.\u003c/p\u003e\n"],["\u003cp\u003eBilling settings for proposals cannot be updated post-approval, potentially resulting in BillingError if modification is attempted.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can use the BillingError details, such as reason and field path, to diagnose and address billing-related issues within their applications.\u003c/p\u003e\n"]]],["The `ProposalService` and `ProposalLineItemService` handle billing, encountering errors like unsupported schedules/caps, missing billing sources/schedules/caps, and invalid billing sources. `BillingError` inherits from `ApiError`, providing details such as field path, trigger, and a string representation. The `BillingError` enum specifies the error reasons, including missing or invalid billing components and disallowed updates. It also handles general API issues through error types such as permission errors and quotas errors.\n"],null,[]]
