[null,null,["上次更新時間：2025-07-26 (世界標準時間)。"],[[["\u003cp\u003eEnsure proper account permissions are set up by your account representative before your application accesses accounts.\u003c/p\u003e\n"],["\u003cp\u003eFamiliarize yourself with Authorized Buyers concepts and the RTB Protocol, particularly if your application will engage in real-time bidding.\u003c/p\u003e\n"],["\u003cp\u003eParent accounts can view and modify resources for themselves and all associated child accounts, while child accounts can only access their own resources.\u003c/p\u003e\n"],["\u003cp\u003eThe Ad Exchange Buyer API uses RESTful architecture, employing HTTP verbs like \u003ccode\u003eGET\u003c/code\u003e, \u003ccode\u003ePUT\u003c/code\u003e, and \u003ccode\u003ePOST\u003c/code\u003e to interact with resources, such as accounts, identified by unique URIs.\u003c/p\u003e\n"],["\u003cp\u003eThe Ad Exchange Buyer API operates using JSON, a common data-interchange format, for representing data structures in a simple, text-based format.\u003c/p\u003e\n"]]],["To access the Ad Exchange Buyer API, you must first configure account permissions and set up a new project in the APIs Console. Parent accounts can view and modify resources for both themselves and associated child accounts, while child accounts are limited to their own resources. The API uses REST architecture, with operations like `list`, `get`, and `update` mapped to HTTP verbs (GET, PUT). Data is formatted using JSON, and resources are accessed via unique URIs. Each account can be identified by a unique resource ID.\n"],null,["# Background\n\nBefore you start\n----------------\n\n1. Ask your account representative to set up proper permissions for accounts your application will access.\n2. If you're unfamiliar with Authorized Buyers concepts, visit the [Authorized Buyers Help Center](//support.google.com/authorizedbuyers/) and experiment with the [user interface](//www.google.com/authorizedbuyers). If your application is expected to perform real-time bidding, read the [RTB Protocol](/authorized-buyers/rtb/start) documentation.\n3. Visit the [APIs Console](//code.google.com/apis/console/?api=adexchangebuyer) to set up a new project. Either sign in to your developer Google account or create an account. You will then be prompted to create a project and sign off on a couple of Terms of Service.\n\nParent and child accounts\n-------------------------\n\nIf you're working within an account structure containing parent and child\naccounts, you may be able to work more effectively if you understand how they\ninteract. The following is a brief summary:\n\n### Child accounts\n\nA user with credentials that grant access to a child account can only\nview and modify resources associated with their account. Child accounts can't\nview or modify resources belonging to other child or parent accounts.\n\n### Parent accounts\n\nA user with credentials that grant access to a parent account can view\nand modify resources for the parent account in addition to all associated\nchild accounts. For operations listing all of a given resource, this user\nwill receive a response including data for their account and all of their\nchild accounts. Note that for other types of requests targeting resources for child seats, a\nparent account will need to specify an `accountId` path parameter for the child\naccount rather than their own `accountId`.\n| **Note:** You should contact your Technical Account Manager if you want to configure an account structure with parent and child accounts.\n\nThe REST API data model\n-----------------------\n\nA resource is an individual data entity with a unique identifier. The\nAccounts resource represents an Authorized Buyers account entry, and is the root\ndata class for the Ad Exchange Buyer API. The API's methods operate on individual\nAccounts resources, and on collections of Accounts resources.\n\nAn [Accounts\nResource](/authorized-buyers/apis/v1.4/accounts) includes: an Account ID, information used in cookie matching,\nbidder locations, the URL to which bid requests are sent, and a request\nto specify the maximum queries per second to be sent by the ad exchange.\n\nIn addition to the Accounts resource and collection, the Ad Exchange Buyer API\ndefines the following data structures:\n\nBidder location\n\n: Bidder locations are structures that are returned with Accounts Resources\n to provide the URL to which the ad exchange should send bid requests and the\n maximum number of queries per second the ad exchange should send. Here is an\n example of a bidder location, expressed in JSON:\n\n ```text\n \"bidderLocation\": [\n {\n \"url\": \"http://bid.url.com/bidder\",\n \"maximumQps\": 1500\n }\n ],\n ```\n\n \u003cbr /\u003e\n\nItems\n\n: Items provide a list of accounts. Here is an example of items, expressed in JSON:\n\n ```objective-c\n {\n \"kind\": \"adexchangebuyer#accountsList\",\n \"items\": [\n accounts Resource\n ]\n }\n ```\n\n \u003cbr /\u003e\n\nSupported operations\n--------------------\n\nYou can invoke three different methods on collections and resources in the\nAd Exchange Buyer API as described in the following table. All operations require\n[authorization](/authorized-buyers/apis/guides/start#prepare-for-authorization).\n\n| Operation | Description | REST HTTP mappings |\n|-----------|------------------------------------------------------------------------------|---------------------------------------------------------------------------|\n| list | Lists all accounts that can be accessed by the currently authenticated user. | `GET` on a collection URI. |\n| get | Gets a specific Accounts resource. | `GET` on a resource URI. |\n| update | Updates a specific Accounts resource. | `PUT` on a resource URI, where you pass in data for the updated resource. |\n\nCalling style\n-------------\n\nREST is a style of software architecture that provides a convenient and consistent approach to requesting and modifying data.\n\nThe term REST is short for \"[Representational State Transfer](https://en.wikipedia.org/wiki/Representational_state_transfer).\" In the context of Google APIs, it refers to using HTTP verbs to retrieve and modify representations of data stored by Google.\n\nIn a RESTful system, resources are stored in a data store; a client sends a request that the server perform a particular action (such as creating, retrieving, updating, or deleting a resource), and the server performs the action and sends a response, often in the form of a representation of the specified resource.\n\nIn Google's RESTful APIs, the client specifies an action using an HTTP verb such as `POST`, `GET`, `PUT`, or `DELETE`. It specifies a resource by a globally-unique URI of the following form: \n\n```\nhttps://www.googleapis.com/apiName/apiVersion/resourcePath?parameters\n```\n\nBecause all API resources have unique HTTP-accessible URIs, REST enables data caching and is optimized to work with the web's distributed infrastructure.\n\nYou may find the [method definitions](https://tools.ietf.org/html/rfc7231#section-4.3) in the HTTP 1.1 standards documentation useful; they include specifications for `GET`, `POST`, `PUT`, and `DELETE`.\n\n### REST in the Ad Exchange Buyer API\n\nThe supported operations map directly to REST HTTP verbs, as described in\n[API operations](#operations).\n\nThe specific format for API URIs are: \n\n```text\nhttps://www.googleapis.com/adexchangebuyer/v1.4/resourceID?parameters\n```\n\nwhere `resourceID` is the identifier for an\nAccounts resource, and *parameters* are any\nparameters to apply to the query. See\n[standard query parameters](/authorized-buyers/apis/standard_params)\nand the\n[reference documentation](/authorized-buyers/apis/v1.4)\nfor details.\n\nThe format of the `resourceID` path extensions\nlets you identify the resource you're currently operating on, for example: \n\n```text\nhttps://www.googleapis.com/adexchangebuyer/v1.4/accounts\nhttps://www.googleapis.com/adexchangebuyer/v1.4/accounts/id\n```\n\nThe full set of URIs used for each supported operation in the API is\nsummarized in the\n[reference documentation](/authorized-buyers/apis/v1.4).\n\nHere's an example of how this works in the Ad Exchange Buyer API.\n\nGet the authenticated user's list of accounts: \n\n```text\nGET https://www.googleapis.com/adexchangebuyer/v1.4/accounts\n```\n\nData format\n-----------\n\n### JSON\n\n\n[JSON](http://en.wikipedia.org/wiki/JSON) (JavaScript Object Notation) is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see [json.org](http://www.json.org/).\n\n\u003cbr /\u003e"]]
