Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Management Model for Resellers

The reseller role is offered to a limited set of partners that offer search-marketing tools and services to a large number of advertisers. The reseller role allows partners to programmatically create new customer accounts. The reseller is billed by invoice for all advertising costs incurred by their customers. The advertiser does not sign up for Bing Ads credentials, and may pay a fee to the reseller. The following sections describe the entity model and credentials for resellers.

Reseller Entity Model

As described in Entity Hierarchy and Limits all advertising activity is organized by customer, which can have one or more accounts. Two or more customer entities play a role in the reseller model. The reseller customer is required, and then the reseller's aggregator user may programmatically create one or more managed customers with the SignupCustomer Service Operation. The aggregator user role is required for SignupCustomer, and is provided solely to resellers.

Upon initial provisioning the reseller customer does not have any accounts to manage. There is an empty customer shell and an Aggregator user. Every time SignupCustomer is called, the following entities are created outside of the reseller customer.

  • A managed customer is created

  • An account is created within the managed customer

For more information about creating reseller managed customers, see Creating Customers.

The following figure shows two child customers created and managed by a reseller. These are referred to as child customers because the billing rolls up to the reseller's payment instrument.

Reseller Entity Model


The single-user (SU) developer token can solely be used to authenticate with the aggregator user. For more information on token types, see Account Permissions and the Developer Token. The aggregator can programmatically manage all accounts across multiple managed customers.

System_CLiX_note Note

As shown in the figure above, resellers have agency status and may also choose to manage client accounts through the agency model. For more information, see Link to Client Accounts.

Credentials and Account Access

The following are the header elements and the corresponding identifiers that a reseller would use.

System_CLiX_note Note

If you use the AuthenticationToken, the UserName and Password elements are ignored. For more information, see Managing User Authentication with OAuth.

Header Element

Owner

AuthenticationToken

The OAuth access token corresponding to the aggregator's linked Microsoft Account.

UserName

The reseller’s aggregator sign-in user name.

System_CLiX_note Note

As a best practice the reseller's aggregator user should always be used. If a unique business requirement is flagged, it is possible to create new users within the managed customers and join them with a multi-user token in calls to some service operations. For more information see Account Permissions and the Developer Token and User Roles and Available Services within Managing Customer Accounts.

Password

The sign-in password of the user specified in UserName.

DeveloperToken

The reseller’s token.

CustomerId

A managed customer ID.

System_CLiX_note Note

Using the reseller customer ID may work for some services, and is not fully supported. As a best practice, use the customer ID which contains the managed account and campaigns.

CustomerAccountId

A managed customer's account ID.

For more information about customer and account identifiers, see Getting Started With the Bing Ads API.

How to Get Reseller API Credentials

To request reseller API credentials, please contact your designated account management team for details about getting the API Reseller role. If you are not currently a reseller but would like to become one, see Become a Microsoft Advertising Authorized Reseller.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.