- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization Scopes
- Try it!
List proposals. A filter expression (PQL query) may be specified to filter the results. To retrieve all finalized proposals, regardless if a proposal is being renegotiated, see the FinalizedProposals resource. Note that Bidder/ChildSeat relationships differ from the usual behavior. A Bidder account can only see its child seats' proposals by specifying the ChildSeat's accountId in the request path.
The URL uses gRPC Transcoding syntax.
Account ID of the buyer.
An optional PQL filter query used to query for proposals.
Nested repeated fields, such as proposal.deals.targetingCriterion, cannot be filtered.
Requested page size. The server may return fewer results than requested. If unspecified, the server will pick an appropriate default.
The page token as returned from ListProposalsResponse.
Syntax the filter is written in. Current implementation defaults to PQL but in the future it will be LIST_FILTER.
The request body must be empty.
If successful, the response body contains an instance of
Requires the following OAuth scope: