Generally not, but there's a few topics to unpack here. For one, we have the concept of buyer types–these include bidders (formerly known as "parent seats") and buyers (formerly known as "child seats"). Some context about those is described in
this Help Center Article.
Additionally, the Ad Exchange Buyer II API represents these slightly differently than the more recent Real-time Bidding and Marketplace APIs. Bidder-level operations are still performed under the
bidders resource (such as
bidders.filterSets), but buyer-level operations are performed under the
accounts resource (such as
bidders.accounts.filterSets). Generally speaking, bidder-level operations can act upon all buyer accounts under it, such as listing filtered bid requests across all buyer accounts. Likewise, buyer-level operations generally act upon a specific buyer, such as listing filtered bid requests for just a given buyer account. We describe this relationship more in the
RTB Troubleshooting Guide.
One caveat to keep in mind though is that a bidder may also act as a buyer–for example, they can upload their own creatives and bid on their own behalf. In these instances, the API
would use the same ID for the bidder and buyer account IDs.
Obtaining these IDs and access to the underlying accounts is a pretty critical part of onboarding; you should probably reach out your account manager if you have one assigned. Otherwise, you could use
this form to get in touch with an account manager. If you happen to already have an integration with configured credentials, you could plausibly use Real-time Bidding API's
bidders and
buyers resources to get the account ID (it is embedded in the resource name). Likewise, if you or someone else on your team has access to the
Authorized Buyers UI, that would also be an option to view account IDs. Account recovery is out of scope for this alias though, so I can't directly assist you with that.