locked
CustomerManagement API RRS feed

  • Question

  • How to get all accounts GetAccounts()?

    Spent 8 hrs and found nothing. Documentation is inadequate. Error message are vague. The error code which I am getting, it's status is TBD.

    It should be as simple as
    CustomerManagement.GetAccounts(authentication);

    Why we need to instantiate 10 different objects to get something like GetAccounts()? I am just frustrated.

    Second Question:
    Why AccountID is required for Keyword Performance report? Why Can't I just get data for all accounts?

    Third Question:
    Why can't you make programmers life easier?





    Friday, February 12, 2010 11:03 PM

All replies

  • Sorry if you are getting frustrated. This link may help:

    http://msdn.microsoft.com/en-us/library/bb126206.aspx

    In general, only 2 objects would need to be instantiated. I don't believe we return TBD as an error status?

    If you pass NULL for AccountID for reports, it will return all accounts. There is also information on our blog here:

    http://community.microsoftadvertising.com/blogs/api/archive/2009/05/28/key-features-amp-changes-in-reporting-api-v6-from-api-v51.aspx

    I would recommend creating a support ticket in the future if you come across an issue that takes more than 30 minutes to figure out, and we would be happy to help.

    Jeff Dillon, API Support

    Saturday, February 13, 2010 1:53 AM
  • Thanks Jeff for looking at the issue.

    Still having some issue. There is no class called CustomerManagement in adCenter.CustomerManagementService

    static void GetAccountIds(ApiUserAuthHeader authHdr)
    {
    // Declare variables.
    adCenter.CustomerManagementService. (I only see CustomerManagementSoap, CustomerManagementSoapChannel, CustomerManagementSoapClient)

    }

    You can't pass Null to AccountIds in AccountThroughAdGroupReportScope for keywrodPerformanceReportRequest to get report for all keywords.

    If you try to do that, you get this message
    The message with Action 'QueueReport' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

    Which doesn't make any sense.
    Monday, February 15, 2010 6:05 PM
  • Please open a support ticket so we can assist you directly. It appears you perhaps didn't specify MessageContracts when creating your local proxy files. There is documenation here:

    http://msdn.microsoft.com/en-us/library/cc148845.aspx

    Jeff Dillon, API Support
    Monday, February 15, 2010 11:51 PM