adCenter API

Scheduled Maintenance on June 23 and June 28

Chris Norred - MSFT — Fri, 20 Jun 2008 22:45:00 GMT

Upgrades on Sandbox and Production services next week might result in some impacts to API customers.

On Monday, June 23rd, an upgrade on the adCenter API Sandbox service is scheduled from 1 p.m. to 2 p.m. PST.

On Saturday, June 28th, an upgrade on the production service is scheduled from 7 p.m. to 8 p.m. PST.

The upgrades might impact signups, updates to accounts, and self-serve billing. Threshold or anniversary billing won't occur during this time.

If you have questions about the work, post them here or in the adCenter API forums

Thank you for using adCenter.

Chris

PDC Announcements of Interest for Developers Working on adCenter API

Chris Norred - MSFT — Fri, 20 Jun 2008 02:50:53 GMT

I just got some info about the Microsoft PDC this fall. adCenter API Developers might be interested.

http://www.microsoftpdc.com/

PDC is about the future and is the event to attend. Just read what Jon Box says, "In my opinion, if I was going to choose one technical event to attend in any year, my first choice will always be the PDC. That's where I became aware of DCOM and ASP, before they came out. That was the year when I first saw Don Box. [more...] Others agree. Follow Andrew Connell as he blogs his way to the PDC. Technical Fellow Brian Harry has announced that the VSTS product team will be talking about what is coming in the Team System release code named "Rosario" and evangelists have flooded the net with posts about Rosario and Brian Randell's pre-con. William H. Salazar posted similar news and joined Brian Keller as they pointed out Brian Randell's . [more...] The news is out. PDC2008 is happening. The buzz can be found on blogs by Jason Olson and Doug Holland. Jason Olson's announcement about Open Space drew the attention of Open Space originator Harrison Owen and Jack Martin Leith commented, "For those who want evidence that Open Space has moved from the fringes to the mainstream, this must surely be it.". [more...] And, two more shameless self-promotion plugs for the Show Off contest came from Brian Keller and Dan Fernandez. Rumor has it they have some great posters and blog bling coming out soon.

How To Set No End Date for an Ad Group in adCenter API version 5.1

Strohm Armstrong - MSFT — Thu, 19 Jun 2008 16:39:00 GMT

When creating an ad group with version 5.1 of the adCenter API, you can specify that the ad group has no end date by passing null for the EndDate element, but if you pass null for the EndDate element when calling the UpdateAdGroups service operation, the existing EndDate value is not modified. So how do you modify an existing ad group to have no end date?

A change was recently made to adCenter API version 5.1 to support updating an ad group to have no end date. When calling the UpdateAdGroups service operation, simply set the EndDate element to a date that is equal to or later than January 2nd, 2050. adCenter will interpret this as specifying no end date for the ad group and take the appropriate action.

Strohm Armstrong
Programming Writer
adCenter API

P.S. Don't forget that adCenter API version 4 will no longer be available after August 14th, 2008. You should be migrating your adCenter code to version 5.1 to avoid any interruptions of service.

A request for the community: adCenter API code in Python?

Chris Norred - MSFT — Tue, 17 Jun 2008 21:06:48 GMT

One of the adCenter API developers, JohnJ, recently posted a request in the API forums for advice on using a python module to use the adCenter API.

API access using python

The API documentation does not discuss the use of the Python Programming Language. I checked with our documentation lead who said the team is not currently working on Python documentation. Also, I haven't seen any posts or heard of other customers who are using the API with Python. Therefore, I thought I would highlight JohnJ's request on the blog in case any of the readers in the API dev community happen to have tried Python and have advice to share.

Thank you,

Chris

adCenter API Documentation for Offline Use

Walter Poupore - MSFT — Tue, 17 Jun 2008 18:29:00 GMT

Hello,

The Microsoft adCenter API documentation on MSDN is the latest documentation for the API.

We're also providing you with the attached Help file, that would allow you to view Help offline. In addition to allowing you to view Help offline, the attached Help file allows you to print topics (including topic nodes), and includes Help search functionality.

Note that the attached Help file requires Windows. Also, the Help file is provided As Is. We won't be able to troubleshoot issues (if any) you have installing and using the Help file. If the Help file doesn't work for your environment, you can always use the adCenter API Help on MSDN.

If you use this attached Help file, it is your responsibility to ensure that you update your copy of the attached Help file when the adCenter API documentation on MSDN is updated. When adCenter API doc updates occur on MSDN, the attachment available here will also be updated (but you'll need to copy it to your computer manually).

You can compare the "What's New in the SDK for Microsoft adCenter API" topic in the attached Help file and What's New in the SDK for Microsoft adCenter API on MSDN to determine if you are using the most current offline Help file.

To download the CHM, scroll down in this page to right above the Comments section.

There you will see "Attachment: adCenterAPI.zip". Download adCenterAPI.zip, unzip it, and you will have the Help file, adCenterAPI.chm.

Thank you.

Walter Poupore
Lead Programming Writer
Microsoft adCenter API

If you have questions or comments, you can discuss this article in the API forums:

Blog Post: Viewing adCenter API Help offline and printing Help to...

adCenter API Live Meeting July 15th at 1 p.m. PST.

Chris Norred - MSFT — Mon, 16 Jun 2008 17:11:00 GMT

Please join us. The adCenter API Live Meeting session is at 10 a.m. tomorrow, Tuesday, June 17th. The earlier time is to accommodate some of our European customers who were having to log on late at night for the sessions.

The deadline for updating all API code is August 14th. These monthly Live Meeting sessions give you a chance to talk with the program manager or members of the development team and ask questions. The team also provides an overview of changes in functionality and updates required.

This month, we'll talk more about the changes required by June 29th for customers who were already on Version 5. We will also cover the necessary updates to prepare for the retirement of API v4 on August 14th.

adCenter API Live Meeting Sessions are held on the third Tuesday of every month. They are recorded and saved on the adCenter API blog http://www.adcentercommunity.com/blogs/api/.

If you have questions that you'd like the team to address, post them in the comments on the blog or in this thread: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3492626&SiteID=1

You can listen to the Live Meetings online, and submit questions via the Live Meeting chat. We will also open a conference call and post the number in the Live Meeting, for those who prefer to call in and listen or talk with the team via phone.

If you have not used Live Meeting before, we recommend visiting API Version 5 Live Meeting a few minutes before the session begins to complete any required installation steps.

Our next webcast will be on July 15th at 1 p.m. PST.

Resources
To learn more about Version 5.1 features, see the Microsoft adCenter API Version 5.1 Release Notes, What's New in the SDK for Microsoft adCenter API. If you have questions, please post to the forums: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=901&SiteID=1

Our next webcast will be on July 15th at 1 p.m. PST. If you would like more opportunities for Live Meeting discussions between now and the August update deadline, please let us know.

-Chris

V5.1 Ad Group Targeting Sample in PHP

Walter Poupore - MSFT — Thu, 12 Jun 2008 22:51:00 GMT

Hello.

Below is an ad group targeting sample written in PHP that uses the V5.1 Campaign Management Web service. We'll include this sample in a future MSDN release.

The Target Class allows you to specify target options for age ranges, days of the week, gender, hour ranges, and location. This specific sample shows how to incrementally bid for specific age ranges. Other target options would use a similar technique.

<?php

// This program requires the following PHP extensions:
// php_soap.dll
// php_openssl.dll

// To ensure that a cached WSDL is not being used,
// disable WSDL caching.
ini_set("soap.wsdl_cache_enabled", "0");

try
{

$adGroupId = 50927722; //Application-specific value.

    // Use either the sandbox or production URI.
    // This example is for the sandbox URI.
    $URI =
        "https://sandboxapi.adcenter.microsoft.com/api/advertiser/v5.1/";
    // The following commented-out line contains the production URI.
    //$URI = "https://adcenterapi.microsoft.com/api/advertiser/v5.1/";

// The adCenter API namespace.
$xmlns = "https://adcenter.microsoft.com/api/advertiser/v5";

    // The proxy for the Campaign Management Web service.
    $campaignProxy =
        $URI . "CampaignManagement/CampaignManagementService.svc?wsdl";

// The name of the service operation that will be called.
$action = "AddTarget";

    // The user name, password, and developer token are
    // expected to be passed in as command-line
    // arguments.
    // $argv[0] is the PHP file name.
    // $argv[1] is the user name.
    // $argv[2] is the password.
    // $argv[3] is the developer token.
    if ($argc !=4)
    {
        printf("Usage:\n");
        printf(
          "php file.php username password devtoken\n");
        exit(0);
    }
    $username = $argv[1];
    $password = $argv[2];
    $developerTokenValue = $argv[3];
    $applicationTokenValue="";

    // Assign the credentials to the classes
    // that are used by the SOAP headers.
    $userCredentials=new UserCredentials();
    $userCredentials->Username=$username;
    $userCredentials->Password=$password;
    $developerToken=new DeveloperToken();
    $developerToken->Value=$developerTokenValue;
    $applicationToken=new ApplicationToken();
    $applicationToken->Value=$applicationTokenValue;

    // Create the SOAP headers.
    $headerApplicationToken =
        new SoapHeader
        (
            $xmlns,
            'ApplicationToken',
            $applicationToken,
            false
        );
    $headerDeveloperToken =
        new SoapHeader
        (
            $xmlns,
            'DeveloperToken',
            $developerToken,
            false
        );
    $headerUserCredentials =
        new SoapHeader
        (
            $xmlns,
            'UserCredentials',
            $userCredentials,
            false
        );

    // Create the SOAP input header array.
    $inputHeaders = array
    (
        $headerApplicationToken,
        $headerDeveloperToken,
        $headerUserCredentials
    );

    // Create the SOAP client.
    $opts = array('trace' => true);
    $client = new SOAPClient($campaignProxy, $opts);

    // Populate an array of age targets, for incremental bids.
    // Incrementally bid 10% on the 18-25–year age group.
    $ageTargetBidArray[] = array(
      "IncrementalBid" => 'TenPercent',
      "Age" => 'EighteenToTwentyFive'
    );

    // Incrementally bid 20% on the 25-35–year age group.
    $ageTargetBidArray[] = array(
       "IncrementalBid" => 'TwentyPercent',
        "Age" => 'TwentyFiveToThirtyFive'
    );

    // Incrementally bid 20% on the 35-50–year age group.
    $ageTargetBidArray[] = array(
       "IncrementalBid" => 'TwentyPercent',
        "Age" => 'ThirtyFiveToFifty'
     );

    // Incrementally bid 20% on the 50-65–year age group.
    $ageTargetBidArray[] = array(
       "IncrementalBid" => 'TwentyPercent',
        "Age" => 'FiftyToSixtyFive'
     );

     // Incrementally bid 30% on the 65-year-and-over age group.
     $ageTargetBidArray[] = array(
       "IncrementalBid" => 'ThirtyPercent',
        "Age" => 'SixtyFiveAndAbove'
     );

     // Assign the age target details
     // array to an ageTarget variable.
     $ageTarget = array
     (
         "Bids" => $ageTargetBidArray
     );

     // Assign the ageTarget variable to
     // a target variable.
     $target = array
     (
         "Age" => $ageTarget
     );

    // Specify the parameters for the SOAP call.
    $params = array
    (
        'AdGroupId'=>$adGroupId,
        'Target'=>$target
    );

    // Execute the SOAP call.
    $result = $client->__soapCall
    (
        $action,
        array( $action.'Request' => $params ),
        null,
        $inputHeaders,
        $outputHeaders
    );

    print "$action succeeded with Tracking ID "
          . $outputHeaders['ApiCallTrackingData']->TrackingId
          . ".\n";

    // Retrieve the ad group IDs.
    if (isset(
        $result->AdGroupIds->int
        ))
    {
        if (is_array($result->AdGroupIds->int))
        {
            // An array of ad group IDs has been returned.
            $obj = $result->AdGroupIds->int;
        }
        else
        {
            // A single ad group ID has been returned.
            $obj = $result->AdGroupIds;
        }
        print "The following ad groups were returned by $action:\n";
        foreach ($obj as $adGroupId)
        {
            print "Ad group ID: " . $adGroupId . "\n";
        }
    }
}

catch (Exception $e)
{
    print "$action failed.\n";
    // Display the fault code and the fault string.
    print $e->faultcode . " " . $e->faultstring . ".\n";

print "TrackingID: " .
$e->detail->ApiFaultDetail->TrackingId . ".\n";

    // Process operation errors.
    if (isset(
        $e->detail->ApiFaultDetail->OperationErrors->OperationError
        ))
    {
        if (is_array(
            $e->detail->ApiFaultDetail->OperationErrors->OperationError
            ))
        {
            // An array of operation errors has been returned.
            $obj =
                $e->detail->ApiFaultDetail->OperationErrors->OperationError;
        }
        else
        {
            // A single operation error has been returned.
            $obj = $e->detail->ApiFaultDetail->OperationErrors;
        }
        foreach ($obj as $operationError)
        {
            print "Operation error " .
                $operationError->Code . " encountered. ";
            print $operationError->Message . "\n";
        }
    }

    // Process batch errors.
    if (isset(
        $e->detail->ApiFaultDetail->BatchErrors->BatchError
        ))
    {
        if (is_array(
            $e->detail->ApiFaultDetail->BatchErrors->BatchError
            ))
        {
            // An array of batch errors has been returned.
            $obj = $e->detail->ApiFaultDetail->BatchErrors->BatchError;
        }
        else
        {
            // A single batch error has been returned.
            $obj = $e->detail->ApiFaultDetail->BatchErrors;
        }
        foreach ($obj as $batchError)
        {
            print "Ad group index " . $batchError->Index . "\n";
            print "Batch error " .
                $batchError->Code . " encountered. ";
            print $batchError->Message . "\n";
        }
    }
}

// Definitions for classes that are used by the SOAP headers.
class ApplicationToken
{
    public $Value;
}
class DeveloperToken
{
    public $Value;
}
class UserCredentials
{
    public $Password;
    public $Username;
}

Thank you.

Walter Poupore
Lead Programming Writer
Microsoft adCenter API

If you have questions or comments about this post, you can discuss it in the API forums:

Blog Post: New ad group targeting sample in PHP using the V5.1 Ca...

http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3499272&SiteID=1&mode=1

adCenter API V5/V5.1 Deadlines approaching - Are you Ready?

bbled — Tue, 03 Jun 2008 15:07:00 GMT

Can you believe it is June already? Back when we released Version 5 of the adCenter API in February (February 14th actually) the summer felt so far away. But, June 3rd reminds us that summer is HERE, and that the deadlines for upgrading your adCenter API-Enabled applications to Version 5/5.1 are approaching fast!

So, we here at the adCenter API Blog have put together some answers for you about the upgrade and encourage you to take a minute to make sure you're on course for the updgrades.

Q. Version 5.1 - What is this?

A. adCenter API users should be receiving email communications from us today regarding an update to the Version 5 adCenter API, Version 5.1. The version is highlighted by 3 small changes:

A change in the keywordID data type from an Int to a Long.
Updates to the Campaign Management Web service to support future expansion of the adCenter API.
Updates to all of the WSDL's to put the v5.1 into their URL's.

Q. What's the reason for these changes when you just came out with a major upgrade in February 08?

A. Since we released Version 5 we have been actively evaluating Version 5 and are making ongoing tweaks and adjustments to ensure that the Microsoft adCenter API is operating as expected. We have identified areas in the CampaignManagement WSDL that need additional improvements. At this time, we have not found an immediate need to update the other WSDLs, Administration, CustomerManagement, NotificationManagement, and Reporting.

The good news here is that while we reserve the possibility of an upgrade as we continue to tune and tweak, we are currently not planning any more upgrades in Calendar 2008.

Q. Wait, I've already implemented V5. Do I have to make more changes for V5.1?

A. Yes, if you've already implemented adCenter API version 5 in your adCenter API-enabled applications, you need to update your applications to use version 5.1 by June 29, 2008. This is a firm date for the change.

Q. But, what if I am WORKING ON Version 5 implementation right now?

A. The overall deadline set back in Feburary for the update to Version 5 of the adCenter API was August, 14, 2008. That date still stands today. Now however, you need to bring your adCenter API-Enabled applications up to V5.1 by that deadline. Remember, adCenter API Version 5 support will end on June 29th, 2008.

Q. What if I haven't started on Version 5 yet?

A. The short answer here is, we need you to get going. We are recommending that you are ready for implementation (testing, etc.) for now version 5.1 of the adCenter API approximately 30 days prior to the August 14, 2008 date. That means we're approximately 6 weeks from what we hope is a completion date for your updates.

Q.Yikes! I need help. What are my options?

Luckily, we ARE here to help. Here are some resources for you to get going:

First step is to click over to the freshly updated MSDN adCenter API Docs. They've got all of the details on what you need to do to get going.
We have lots of good samples for V5/5.1 here in the adCenter API blog as in a variety of supported languages. Watch the blog for more to come as new examples are published.
We've been running monthly Live Meeting's with the Senior Project management team from the adCenter API, all of which are recorded and posted here on adCentercommunity.com. Here's a link to the May Session for a good question and answer session, as well as some background on the V5.1 changes. Our next session is scheduled for June 17, 2008.
Contact your service team members! Members of the API Technical Support and adCenter client service teams are here to help. If you have questions, challenges, etc. now is the time to get in touch with us. We can get you the resources you need to facilitate this upgrade.

Summary:

We are excited about the new features we have to offer in the Version 5/5.1 upgrade. However, we definitely understand that enabling these requires changes in your applications. With the announcement of the Version 5 release back in February we allowed 180 days of upgrade time prior to shutting down V4 support. We're approaching that deadline however, so if you haven't gotten started on this upgrade, now is the time. Good luck, and as always thanks for choosing to support the adCenter platform via the adCenter API.

Cheers,

Bill

Ask questions or discuss this topic in the adCenter API Development forums.

V5.1 Reporting Sample in PHP

Walter Poupore - MSFT — Mon, 02 Jun 2008 16:31:00 GMT

Hello!

We'll release a V5.1 reporting sample in PHP to MSDN in a future Microsoft adCenter API doc release.

In the interim, here is the sample. Note the $URI variable is set to V5.1. If you want to use the V5 WSDL, set "V5.1" to "V5". You're encouraged to use the V5.1 version, though, as V5.1 is the latest version.

<?php

// This program requires the following PHP extensions:
// php_soap.dll
// php_openssl.dll

// To ensure that a cached WSDL is not being used,
// disable WSDL caching.
ini_set("soap.wsdl_cache_enabled", "0");

try
{

$accountId = 489; //Application-specific value.

// The adCenter API namespace.
$xmlns = "https://adcenter.microsoft.com/api/advertiser/v5";

    // The proxy for the Campaign Management Web service.
    $campaignProxy =
        $URI . "Reporting/ReportingService.svc?wsdl";

// The name of the service operation that will be called.
$action = "QueueReport";

    // The user name, password, and access key are
    // expected to be passed in as command-line
    // arguments.
    // $argv[0] is the PHP file name.
    // $argv[1] is the user name.
    // $argv[2] is the password.
    // $argv[3] is the developer token.
    if ($argc !=4)
    {
        printf("Usage:\n");
        printf(
          "php file.php username password devtoken\n");
        exit(0);
    }
    $username = $argv[1];
    $password = $argv[2];
    $developerTokenValue = $argv[3];
    $applicationTokenValue="";

    // Create the SOAP input header array.
    $inputHeaders = array
    (
        $headerApplicationToken,
        $headerDeveloperToken,
        $headerUserCredentials
    );

    // Create the SOAP client.
    $opts = array('trace' => true);
    $client = new SOAPClient($campaignProxy, $opts);

    $request=new KeywordPerformanceReportRequest();
    $request->Format='Xml';
    $request->Language='English';
    $request->ReportName='My Report';
    $request->ReturnOnlyCompleteData=false;
    $request->Aggregation='Monthly';
    $request->Time=array('PredefinedTime'=>'LastSixMonths');

    $request->Columns=array('AccountName',
                            'CampaignName',
                            'Keyword',
                            'TimePeriod',
                            'ProductName',
                            'Impressions',
                            'Conversions');

    $request->Filter=array('AdDistribution'=>'Search',
                           'LanguageAndRegion'=>'UnitedStates');
    $request->Scope=array('AccountIds'=>array($accountId));

    $soapstruct = new SoapVar($request,
                              SOAP_ENC_OBJECT,
                              "KeywordPerformanceReportRequest",
                              $xmlns);

$params=array('ReportRequest'=>$soapstruct);
$result = $client->__soapCall($action,array($action.'Request' => $params),null,$inputHeaders,$outputHeaders);

    $reportRequestId=$result->ReportRequestId;
    printf("ReportRequestId: %d\n", $reportRequestId);
    // Poll to get the status of the report until it is complete.
    $waitMinutes = 15;
    $maxWaitMinutes = 120;
    $elapsedMinutes = 0;
    $action = "GetReportStatus";
    $params=array('ReportRequestId'=>$reportRequestId);
    while (true)
    {

        // Wait the specified number of minutes before you poll.
        printf("Waiting another %d minutes.\n",
               $waitMinutes);
        printf("Total wait time so far is %d minutes.\n",
               $elapsedMinutes);
        sleep($waitMinutes * 60);
        $elapsedMinutes += $waitMinutes;

$result = $client->__soapCall($action,array($action.'Request' => $params),null,$inputHeaders);

        $reportStatus=$result->ReportRequestStatus->Status;
        printf("ReportStatus: %s\n", $reportStatus);
        if ($reportStatus == 'Success')
        {
            $downloadURL=$result->ReportRequestStatus->ReportDownloadUrl;

$handleIn = fopen($downloadURL,"r");
$handleOut = fopen($reportRequestId.".zip", "w");

            while (!feof($handleIn))
            {
              $content = fread($handleIn, 8192);
              fwrite($handleOut,$content);
            }
            fclose($handleIn);
            fclose($handleOut);
            break;
         }
         else
         {
               if ($reportStatus == 'Pending')
                {
                    // The report is not yet ready.
                    continue;
                }
                else
                {
                    // An error occurred.
                    printf("Error occurred in %s\n", $action);
                    break;
                }
          }
      }
}

catch (Exception $e)
{
    print "$action failed.\n";
    // Display the fault code and the fault string.
    print $e->faultcode . " " . $e->faultstring . ".\n";

print "TrackingID: " .
$e->detail->ApiFaultDetail->TrackingId . ".\n";

    // Process operation errors.
    if (isset(
        $e->detail->ApiFaultDetail->OperationErrors->OperationError
        ))
    {
        if (is_array(
            $e->detail->ApiFaultDetail->OperationErrors->OperationError
            ))
        {
            // An array of operation errors has been returned.
            $obj = $e->detail->ApiFaultDetail->OperationErrors->OperationError;
        }
        else
        {
            // A single operation error has been returned.
            $obj = $e->detail->ApiFaultDetail->OperationErrors;
        }
        foreach ($obj as $operationError)
        {
            print "Operation error " .
                $operationError->Code . " encountered. ";
            print $operationError->Message . "\n";
        }
    }

    // Output the last request.
    print "Last SOAP request:\n";
    print $client->__getLastRequest() . "\n";
}

// Definition for class used by the Reporting service.
class KeywordPerformanceReportRequest
{
    public $Format;
    public $Language;
    public $ReportName;
    public $ReturnOnlyCompleteData;
    public $Aggregation;
    public $Columns;
    public $Filter;
    public $Scope;
    public $Time;
}

Thank you.

Walter Poupore
Lead Programming Writer
Microsoft adCenter

adCenter API forums back online

Chris Norred - MSFT — Fri, 30 May 2008 17:31:36 GMT

We had some issues yesterday with the API forums during a migration of the MSDN system but the problems appear to be resolved. Apologies for the inconvenience. Please let us know if you encounter any ongoing issues with the forum by posting via the blog comments, the Advertiser forum on this site. Also, you can send a message to the support alias for API users or to me via the web site.

Thanks for taking part in the community.

Chris

Webcast recording from adCenter API v5 update Live Meeting

Chris Norred - MSFT — Thu, 29 May 2008 23:13:00 GMT

In last week's webcast, Program Manager Shamit Patel emphasized the deadline for API users to update code to use version 5 of the adCenter API. His point was that developers should update soon to allow time for testing and troubleshooting implementation of the new code. With summer vacations approaching, now is the time to move to V5.

The Live Meeting last week discussed some new questions from customers and included a walkthrough of the basic changes. View the Webcast below in Silverlight streaming media. Or download the video with the link below.

-Thanks

Chris

Possible API interruptions tonight during server maintenance

Chris Norred - MSFT — Thu, 29 May 2008 21:53:35 GMT

An e-mail communication was sent this afternoon on this. As our API forum is still experiencing some issues, contact support, or post in the comments or Advertiser forum if you have questions.

The Editorial database servers will undergo a short maintenance today, May 29 from 6:00 P.M. to 9:00 P.M. Pacific Time. There may be intermittent interruptions in the availability of editorial-related API calls during this time. No other downtime is expected.

We appreciate your patience while we perform this system maintenance. We apologize for any inconvenience that these intermittent interruptions may cause.

Thanks

Chris

Notice of adCenter API forums issues

Chris Norred - MSFT — Thu, 29 May 2008 19:46:25 GMT

We are currently experiencing some downtime in the adCenter API forums on MSDN. The forum databases are being migrated and there is a current issue related to the content of new posts not being displayed. If you're experiencing issues, please use the API support alias for help, or post in the Advertiser forum or in the comments of the blog with other questions and comments. We'll attempt to engage there until the MSDN forum issues can be resolved. We expect the issues to be resolved soon.

Thank you for your patience and thanks for taking part in the community.

Chris

SOAP XML Sequence in adCenter API

Strohm Armstrong - MSFT — Thu, 22 May 2008 17:11:00 GMT

There was a question during the Live Meeting this week regarding the correct sequence for SOAP XML elements when programming with the adCenter API. I previously published a helpful blog entry offering guidance on the SOAP XML Property Order. Check it out here:

http://www.adcentercommunity.com/blogs/api/archive/2008/03/27/soap-xml-property-order-is-important.aspx

We are gradually adding what we refer to as "WSDL syntax" to the adCenter API V5 reference topics. This additional syntax will help those of you who are assembling your SOAP messages manually. This is an ongoing process and the new syntax will be published along with our scheduled updates. To see what this will look like, see the Report Request Class topic on MSDN.

As always, feedback on this and other adCenter API documentation is welcome.

Thank You,

Strohm Armstrong
Programming Writer
adCenter API

Using adCenter API Version 5 with Microsoft .NET Framework Version 2.0

Strohm Armstrong - MSFT — Thu, 22 May 2008 16:58:00 GMT

During the adCenter API Live Meeting this week, one of the participants asked Program Manager Shamit Patel if we have published any documentation explaining how to use adCenter API V5 with .NET 2.0.

The short answer is that you must use .NET Framework 3.0 for your .NET applications when using adCenter API version 5. Here is why:

The client proxies that get generated for the WCF services use the IExtensibleDataObject interface, which is only available in .NET 3.0.
To use adCenter API V5 with a .NET language, you have to use two assemblies that are only available in .NET 3.0 and later, System.Runtime.Serialization and System.ServiceModel.

However, many people don't realize that .NET 3.0 is an addition to the framework, not a complete replacement. You will still use .NET Framework 2.0 for the majority of your application. .NET 3.0 does not, in fact, include any of the legacy assemblies (e.g. System.Xml), so you actually use .NET 2.0 for most everything else in your application.

The end result is that the documentation and code samples provided on MSDN and the blog will help you with using .NET 2.0, but you must add .NET 3.0 and the required references to System.Runtime.Serialization.dll and System.ServiceModel.dll.

Thanks You,

Strohm Armstrong
Programming Writer
adCenter API