Due to system upgrades taking place from 7:00 p.m. PDT on Wednesday, October 14
to 10:00 a.m. PDT on Thursday, October 15, API calls sent to the EWS 21, EWS 22
and EWS 23 endpoints may experience some service degradation. We apologize for
any inconvenience this may cause you. If you have further questions or require
additional assistance, please email ews-help@... or contact your
Account Manager.

Upcoming Systems Maintenane on 10/19/2009

Due to system upgrades taking place from 6:00 a.m. PDT on Monday, October 19 to
6:00 p.m. PDT on Friday, October 23, you may experience some service
degradation. Additionally, there may be some reporting delays during this
period. We apologize for any inconvenience this may cause you. If you have
further questions or require additional assistance, please email
ews-help@... or contact your Account Manager.



Upcoming Systems Maintenance on 10/16/2009

No API calls to the EWS12 and EWS13 endpoints will be serviced for approximately
six hours, beginning at 6:00 p.m. PDT on Friday, October 16 and ending at 12:00
a.m. PDT on Saturday, October 17. Additionally, reporting data will not be fully
loaded until approximately 10:00 a.m. PDT on October 17. Both the API and the
user interface will be affected by this maintenance. Please note that this
maintenance only affects accounts on the EWS12 and EWS13 endpoints--other
endpoints will not be affected.

You will only be affected if the URL Prefix begins with "https://ews11..." or
"https://ews31...".


--- In yws-searchmarketing@yahoogroups.com, Ravi Jain <imdbest.ravi@...> wrote:
>
> Hi,
> How do I found out which end point am i using?
> Thanks.
> - Ravi
>
> On Sat, Oct 3, 2009 at 8:25 AM, mcnealysm <mcnealysm@...> wrote:
>
> >
> >
> > 10/09/2009:
> >
> > No API calls to the EWS11 and EWS31 endpoints will be serviced for
> > approximately ten hours, beginning at 6:00 p.m. PDT on Friday,
> > October 9 and ending at 4:00 a.m. PDT on Saturday, October 10.
> > Additionally, reporting data will not be fully loaded until
> > approximately 4:00 a.m. PDT on October 10. Both the API and the user
> > interface will be affected by this maintenance. Please note that this
> > maintenance only affects accounts on the EWS11 and EWS31 endpoints �"
> > other endpoints will not be affected.
> >
> > 10/11/2009:
> >
> > No API calls to the EWS31 endpoint will be serviced for approximately
> > four hours, beginning at 4:00 p.m. PDT on Sunday, October 11 and
> > ending at 8:00 p.m. PDT. Additionally, reporting data will not be
> > fully loaded until approximately 6:00 a.m. PDT on Monday, October 12.
> > Both the API and the user interface will be affected by this
> > maintenance. Please note that this maintenance only affects accounts
> > on the EWS31 endpoint�"other endpoints will not be affected.
> >
> >
> >
>
>
>
> --
> इतने शिद्दत से तुम्हे पाने की
कोशिश की हैं |
> की हर ज़र्रे मुझे तुमसे
मिलाने की साज़िश की हैं ||
>

What URL Prefix is returned when you call getMasterAccountLocation?

--- In yws-searchmarketing@yahoogroups.com, Ravi Jain <imdbest.ravi@...> wrote:
>
> Hi,
> How do I found out which end point am i using?
> Thanks.
> - Ravi
>
> On Sat, Oct 3, 2009 at 8:25 AM, mcnealysm <mcnealysm@...> wrote:
>
> >
> >
> > 10/09/2009:
> >
> > No API calls to the EWS11 and EWS31 endpoints will be serviced for
> > approximately ten hours, beginning at 6:00 p.m. PDT on Friday,
> > October 9 and ending at 4:00 a.m. PDT on Saturday, October 10.
> > Additionally, reporting data will not be fully loaded until
> > approximately 4:00 a.m. PDT on October 10. Both the API and the user
> > interface will be affected by this maintenance. Please note that this
> > maintenance only affects accounts on the EWS11 and EWS31 endpoints �"
> > other endpoints will not be affected.
> >
> > 10/11/2009:
> >
> > No API calls to the EWS31 endpoint will be serviced for approximately
> > four hours, beginning at 4:00 p.m. PDT on Sunday, October 11 and
> > ending at 8:00 p.m. PDT. Additionally, reporting data will not be
> > fully loaded until approximately 6:00 a.m. PDT on Monday, October 12.
> > Both the API and the user interface will be affected by this
> > maintenance. Please note that this maintenance only affects accounts
> > on the EWS31 endpoint�"other endpoints will not be affected.
> >
> >
> >
>
>
>
> --
> इतने शिद्दत से तुम्हे पाने की
कोशिश की हैं |
> की हर ज़र्रे मुझे तुमसे
मिलाने की साज़िश की हैं ||
>

No API calls to the EWS12 and EWS13 endpoints will be serviced for approximately
six hours, beginning at 6:00 p.m. PDT on Friday, October 16 and ending at 12:00
a.m. PDT on Saturday, October 17. Additionally, reporting data will not be fully
loaded until approximately 10:00 a.m. PDT on October 17. Both the API and the
user interface will be affected by this maintenance. Please note that this
maintenance only affects accounts on the EWS12 and EWS13 endpoints--other
endpoints will not be affected.

In the fourth quarter of 2009, Yahoo! Search Marketing is planning to launch a new version of the Enterprise Web Services (EWS) Marketing API. EWS Version 6.0 is a major version release and includes features that are backward-incompatible. EWS Version 6.0 has been released to the EWS sandbox.

What Do I Need to Do?
We suggest that you first experiment with Version 6.0 in the EWS sandbox, make any required changes to your client application and test your implementation. Then, be ready to switch over to production when the product release is ready.

About this Release
�    EWS Version 6.0 has been released to the EWS sandbox.
�    The production release will occur approximately 30 days after the sandbox release.
�    While EWS Version 5.x.x will continue to be available in production for 120 days after EWS Version 6.0 is released, we recommend that you switch to Version 6.0 as soon as possible.
�    EWS Version 5.x.x will not be available after the 120-day transition period ends.
�    This release is backward-incompatible. To take advantage of the new features, you will need to re-compile your code against Version 6.0 WSDLs.

New Features
The new features and changes in EWS Version 6.0 are summarized below.

Profile APIs Added for Network Distribution
�    EWS APIs will allow setting network distribution using targeting service. In this release, profile APIs (typed APIs) will be available. Please note that framework APIs to support network distribution is already available in EWS v5.2.
�    The network distribution feature is currently available in AU market, which includes Australia and New Zealand. It is tentatively scheduled for availability in the U.S. market in early Q1 2010
�    For more information about Network Distribution, please visit our documentation here.

Domain Blocking in Japan (JP) Market
�    Domain Blocking is now available in JP Market. See AccountService .

Reporting APIs
�    A new API getBooksClosedTime is introduced that will provide advertisers with the Books Closed Date and Time for a given report.
�    The APIs used to retrieve reports have changed. See Section below on Changes to Services.
�    The Targeting Reports will now have Conversion Metrics by default.

Changes to Services

Removed Services
     UpgradeService

Changes to BasicReportService
Following are changes to the BasicReportService

     New Operations
          addReportRequest 
          getReportDownloadUrl 
          getReportDownloadUrls
          getBooksClosedTime

     Removed Operations
          addReportRequestForAccountID
          addReportRequestWithAccountAggregation
          getReportOutputUrl
          getReportOutputUrls

     New Data Objects
         ReportDownloadInfo

New Operations and Modified Data Objects
Please refer to EWS v6.0 release notes to get the full list of new operations and data objects added in EWS v6.0

http://developer.searchmarketing.yahoo.com/docs/changelog.php


Questions?
For more information about our versioning process, please read our Versioning FAQs. If you have further questions, please contact your Technical Solutions Manager or visit our support page here.

I am developing YahooEWSClient.php and request the file nusoap, more specific
function Call it returns this error "( [faultcode] => soap:Client [faultstring]
=> Invalid parameter. [detail] => Array ( [ApiFault] => Array ( [code] => E1021
[message] => Invalid parameter. ) ) )".

Can anyone help me?

10/09/2009:

No API calls to the EWS11 and EWS31 endpoints will be serviced for
approximately ten hours, beginning at 6:00 p.m. PDT on Friday,
October 9 and ending at 4:00 a.m. PDT on Saturday, October 10.
Additionally, reporting data will not be fully loaded until
approximately 4:00 a.m. PDT on October 10. Both the API and the user
interface will be affected by this maintenance. Please note that this
maintenance only affects accounts on the EWS11 and EWS31 endpoints �
other endpoints will not be affected.

10/11/2009:

No API calls to the EWS31 endpoint will be serviced for approximately
four hours, beginning at 4:00 p.m. PDT on Sunday, October 11 and
ending at 8:00 p.m. PDT. Additionally, reporting data will not be
fully loaded until approximately 6:00 a.m. PDT on Monday, October 12.
Both the API and the user interface will be affected by this
maintenance. Please note that this maintenance only affects accounts
on the EWS31 endpoint�other endpoints will not be affected.

Yahoo! Search Marketing is planning to launch a new version of the Enterprise Web Services (EWS) Marketing API in the next 60 days. EWS Version 6.0 will be a major version release, and includes features that are backward-incompatible.

About this Release

New Features � Network Distribution
Using Network Distribution, advertisers may set up campaigns or ad groups targeted to Yahoo! Search, Yahoo! Partners, or both. See: TargetingService. If advertisers choose to set up a campaign at Entire Network (i.e., both Yahoo! Search and Yahoo! Partners), they have the ability to fine-tune their bids by providing Discounts/Premiums on the Yahoo! Partners.

Hi, 200 units should be enough for what you're trying to do.  How often are you
polling the report service to check if the reports are ready?  This can use a
lot of units if you do it too often.

HI ,

I have a master account which has about 20 sub account under it.Ther master
account is a sub account by itself.
I have a windows service which runs to pull the AdKeywordSummaryByDay report.But
my problem is using it with addReportRequestWithAccountAggregation function.The
reason is i have only 200 quota and it exhaust when i pull down by each account.
My windows service is developed in VB.net and i need some help how to do it.

I have included the yahoo api as a web refernence and i am using the below code.


This code below is to get the location url.Where i pass the master account id
and master account username and password.
  Dim serviceLoc As developer.LocationServiceService = New
developer.LocationServiceService
                     serviceLoc.masterAccountIDValue = New
developer.masterAccountID
                     serviceLoc.masterAccountIDValue.Text = New String()
{yh_masterAccountID}
                     serviceLoc.SecurityValue = New developer.Security
                     serviceLoc.SecurityValue.UsernameToken = New
developer.UsernameToken
                     serviceLoc.SecurityValue.UsernameToken.Username =
yh_userName
                     serviceLoc.SecurityValue.UsernameToken.Password =
yh_password
                     serviceLoc.licenseValue = New developer.license
                     serviceLoc.licenseValue.Text = New String() {yh_license}
                     Dim urlLoc As String = ""
                     urlLoc = serviceLoc.getMasterAccountLocation()


  THis line Set up service connection. MAsteraccountid i am passing a sub account
id.IS it correct
                                 Dim service As
developer.BasicReportServiceService = New developer.BasicReportServiceService
                                 ' Define SOAP headers.
                                 service.masterAccountIDValue = New
developer.masterAccountID
                                 service.masterAccountIDValue.Text = New String()
{yh_masterAccountID}
                                 service.SecurityValue = New developer.Security
                                 service.SecurityValue.UsernameToken = New
developer.UsernameToken
                                 service.SecurityValue.UsernameToken.Username =
yh_userName
                                 service.SecurityValue.UsernameToken.Password =
yh_password
                                 service.licenseValue = New developer.license
                                 service.licenseValue.Text = New String()
{yh_license}
                                 service.Url = urlLoc + "/V5/BasicReportService"

                                 '' Create report job structure.
                                 Dim req As developer.BasicReportRequest = New
developer.BasicReportRequest

                                 'req.reportName = "YahooReport"
                                 'req.startDate = "3/21/2009" ''m/d/yyyy
                                 'req.endDate = "3/21/2009"   ''m/d/yyyy
                                 'req.reportType = ""
                                 stDate = yh_startDate
                                 stDate = stDate.AddDays(i)
                                 'Dim reqDate As DateTime = "1/11/2009"
''m/d/yyyy
                                 reqDate = stDate.Month.ToString + "/" +
stDate.Day.ToString + "/" + stDate.Year.ToString ''m/d/yyyy
                                 'reqDate = reqDate.AddDays(i).Date
                                 req.startDate = reqDate
                                 req.startDateSpecified = True
                                 req.endDate = reqDate
                                 req.endDateSpecified = True
                                 req.reportName = "yhMarketingReport_" +
yh_userName + "_" + Date.Now().Date.ToString
                                 req.reportType =
developer.BasicReportType.AdKeywordSummary
                                 req.reportTypeSpecified = True

                                  Dim jobId As Long =
service.addReportRequestWithAccountAggregation(req)


i am not sure whether i am doing it right.if some has used or some documentation
it would help me it would be greta

regards
deepak

Yahoo! Search Marketing has released Enterprise Web Services (EWS) Marketing API Version 5.2.0 in our production and sandbox environment. EWS Version 5.2.0 is a minor-version release and includes features that are backward-compatible. Please click here for more information.

Our program has been working fine until today, we received following error when
calling "getCampaignsByAccountID":

<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Body><soap:Fault><fa\
ultcode>soap:Server</faultcode><faultstring>An internal error has
occurred.</faultstring><detail><ApiFault
xmlns="http://marketing.ews.yahooapis.com/V5"><code>E1002</code><message>An
internal error has
occurred.</message></ApiFault></detail></soap:Fault></soap:Body></soap:Envelope>

is there anyone has the same problem? or this is a Yahoo problem?

I did not change anything in the code and it has been working fine before.

My query string looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://marketing.ews.yahooapis.com/V5">
<soap:Header>
<wsse:Security>
<wsse:UsernameToken>
<wsse:Username>xxxx</wsse:Username>
<wsse:Password>yyyyyy</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<license>
AAAAAAAAAAAAA</license>
<masterAccountID>123344</masterAccountID>
<accountID>234556666</accountID>
<onBehalfOfUsername>xxxxx</onBehalfOfUsername>
<onBehalfOfPassword>yyyyy</onBehalfOfPassword>
</soap:Header>
<soap:Body>
<getCampaignsByAccountID>
<accountID>3456789</accountID>
<includeDeleted>false</includeDeleted>
</getCampaignsByAccountID>
</soap:Body>
</soap:Envelope>

Can anyone help?

I did take a look at the docs, and they state:
Invalid status means "You have specified a status type which is invalid, or you
have attempted to illegally change the status of an object.". However, I am
unable to determine what does an 'illegal change of the status' means.

I have a Deleted campaign that is throwing an exception with that error whenever
I try to update it's status. The strange thing is I cannot reproduce that in
another account I have.

Did anyone encountered the same problem, or has a more precise idea of the
scenarios that represent an illegal status change?

Thanks in advance,
Juan

EWS Version 5.0.0 exposes two sets of interfaces to manage targeting (geo
targeting & much more) at the campaign level. The first set of interfaces allow
managing targeting in a "generic" way - using "targeting ids". The second set
allows managing targeting via specific "typed" TargetingProfile objects which
encapsulate multiple targeting definitions.

Please read the following documentation for details :
1. Targeting Service - A new service (since Version 5.0.0) that can be used to
manage targeting :
http://developer.searchmarketing.yahoo.com/docs/V5/gsg/TargetingService.php
2. Targeting Service Overview - Help to get started using the TargetigService :
http://developer.searchmarketing.yahoo.com/docs/V5/reference/services/TargetingS\
ervice.php



--- In yws-searchmarketing@yahoogroups.com, "deraider" <deraider@...> wrote:
>
> EWS Version 5.0.0 removed setGeographicLocationForCampaign method. We used it
in our project. What methods should we use now to substitute it?
>

EWS V5 supports downloading of the entire account structure a.k.a bulk download.

Documentation can be found here :
http://developer.searchmarketing.yahoo.com/docs/V5/reference/services/BulkServic\
e.php



--- In yws-searchmarketing@yahoogroups.com, "dougleeper" <dougleeper@...> wrote:
>
> Not sure if this is the place to request this but I thought I would try first
here.
>
> I would like to be able to (in a single op) request an account structure
report that would give me all the campaigns, ad groups, keywords, and ads in
single request.  I don't need any performance information...only the current
information of the account as defined by the API.
>
> Currently, I am having to create an application to traverse the account
structure to obtain the necessary information.  While effective, it is
inefficient.
>
> If this feature already exists, can someone point me to is location?  If this
enhancement is in the works, can someone indicate when it will be available?
>
> Thanks in advance.
> Doug
>

i have noticed that contrary to the description "aggregates by keyword", that
this report type aggregates by keyword AND Ad. This is inconsitant with the way
reports are downloaded from the UI, requiring extra developement to support
importing both manualy and aumatically downloaded reports. Is there a basic
report type that gives ALL the same info in the KeywordSummary report that does
not split information for a keyword for different Ads? i.e. "Aggregates by
Keyword"?

Thanks in advance to anyone that looks into this...


-Kristen

Did anyone ever post the .NET sample code? Can someone email me the code?

Thanks

--- In yws-searchmarketing@yahoogroups.com, "m4mjay" <m4mjay@...> wrote:
>
>
> i need sample code as well..plz send me too..thanks!
>
> --- In yws-searchmarketing@yahoogroups.com, "hmcclungiii"
> <hmcclungiii@> wrote:
> >
> > I have written numerous reporting applications in .NET for Windows,
> > would you be interested in this?
> >
> > --- In yws-searchmarketing@yahoogroups.com, "Nicholas Andonakis"
> > <nandonakis@> wrote:
> > >
> > > Hi,
> > >
> > > 1. I need to develop some scripts (php or perl) to query the Yahoo
> > > Search Marketing/EWS API in a hurry and couldn't find any sample
> code,
> > > only the API definition. As far as I can tell, the sample code
> > > provided by yahoo doesn't even include the actual functions for
> the
> > > report service?
> > > Does anybody have any sample code to generate and retrieve
> reports?
> > >
> > > 2. Has anybody used the
> > > phpEWS Enterprise Web Services API
> > > http://sourceforge.net/projects/phpews/
> > > for reporting?
> > >
> >
>

I submitted the sandbox request last Saturday but get no response from Yahoo. Is
there anything wrong?

Thanks

EWS Version 5.0.0 removed setGeographicLocationForCampaign method. We used it in
our project. What methods should we use now to substitute it?

Hi !

Does anyone have a ruby code example to get connected to the yahoo webservice to
get information about an account ?

--- In yws-searchmarketing@yahoogroups.com, "Yahoo! Search Marketing Monkey"
<plummerm@...> wrote:
>
> > Okay, the sample .NET code doesn't implement the BasicReportRequest
> > object and the other line explaining .NET implementation of the
> > timezone specifically states "if your accounts reside in the same
> > time zone as the servers that are running the code, you do not need
> > to modify your code.".  Why is the BasicReportService modifying my
> > timezone when the report is returned?  The WSDL translates the date
> > properties in the BasicReportRequest to the Date type...not
> > dateTime.
>
> There's no modification going on on the server side.  It's
> interpretation.  Remember that the server won't know what timezone you
> are in, so you need to specify dateTime with a timezone offset properly.
>   I'm not sure what you meant by the last sentence.
>
> > Again, what time should I use for the start and end dates?  12am to
> > 11:59pm?  Or does it matter?  Since I am requesting the report in PST
> > will the report return the correct information for that date (even
> > though the report shows an earlier date with the PST timezone) or is
> > it actually the previous day's statistics?
>
> Assume that the date returned is indeed the date reported on.  If you
> pass in a dateTime object with UTC offsets, you'll get the correct
> expected response.  I am not 100% sure about using 12am or 11:59pm, but
> a small bit of experimentation should do the trick.  Reports really
> aren't able to be pulled for specific times, only full days, so using
> dateTime is a bit of a misnomer, but still the required usage for now.
>
> Hope this helps,
> -Y!SM Monkey
>

I'm not sure if anyone is still replying to this thread, but here goes

So from what I gather, all I have to do in order to ensure the correct reporting
dates is to convert the local dateTime to UTC prior to submitting the request.
Is that right?