API Changes Take Effect Today
AdWordsAPIAdvisor
(http://adwordsapi.blogspot.com/2006/04/revisions-to-adwords-api-beta-program.html),
today marks the start of the new AdWords API Beta program terms and
conditions. Starting today, the current developer quota limits have
been abandoned and developers will begin to accrue charges at the rate
of $0.25/1000 quota units consumed (or local currency equivalent). We
believe these changes will result in more flexible and scalable system
for quota allocation and consumption.
You can find more information on the billing process at
http://www.google.com/support/adwordsapi/bin/answer.py?answer=46894.
If you are having difficulty accessing the AdWords API, please verify
that you have completed your registration
(http://adwordsapi.blogspot.com/2006/08/important-api-registration-process-now.html)
and have incorporated your approved Developer Token and Application
Token into your API request headers
(http://www.google.com/apis/adwords/developer/index.html#adwords_api_intro_request).
-- Rohit Dhawan, Product Manager
Richard Jones
> As we first announced on April 11, 2006
> (http://adwordsapi.blogspot.com/2006/04/revisions-to-adwords-api-beta-program.html),
> today marks the start of the new AdWords API Beta program terms and
> conditions. Starting today, the current developer quota limits have
> been abandoned and developers will begin to accrue charges at the rate
> of $0.25/1000 quota units consumed (or local currency equivalent).
Since we're paying for it now, can we expect bugs like the "No_reply"
bug and the "Either this object does not exist, or this user does not
have permission to access it" bug to be fixed?
Both of these bugs are making the API unusable at the moment, and have
been going on for weeks.
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Internet Marketing and AdWords courses - http://merjis.com/courses - NEW!
Merjis blog - http://blog.merjis.com - NEW!
Erik
Tuesday, we experienced a 10% failure rate (2500 failure). I haven't
tried to calculate today, because I am busy adding more detailed error
tracking to our code. So far, things are better (30 ~5/6am EST, 30
6/7am EST, and 20 8/9 pm EST), but it is still unacceptable.
We have been trying to sort this out with the support staff, but they
won't even respond. I can't believe they haven't gone to a trouble
ticketing system yet. Sure hope some of those smart people they've
hired address supporting this system.
/Erik
On Nov 2, 5:46 am, Richard Jones <r...@annexia.org> wrote:
> On Wed, Nov 01, 2006 at 10:58:53PM -0000, AdWordsAPIAdvisor wrote:
> > As we first announced on April 11, 2006
> > (http://adwordsapi.blogspot.com/2006/04/revisions-to-adwords-api-beta-...),
> > today marks the start of the new AdWords API Beta program terms and
> > conditions. Starting today, the current developer quota limits have
> > been abandoned and developers will begin to accrue charges at the rate
> > of $0.25/1000 quota units consumed (or local currency equivalent).Since we're paying for it now, can we expect bugs like the "No_reply"
> bug and the "Either this object does not exist, or this user does not
> have permission to access it" bug to be fixed?
>
> Both of these bugs are making the API unusable at the moment, and have
> been going on for weeks.
>
> Rich.
>
> --
> Richard Jones, CTO Merjis Ltd.
> Merjis - web marketing and technology -http://merjis.com
tom.mancino
internal error on:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>An internal error has occurred. Please retry your
request.</faultstring>
<detail>
<ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/v6">
<ns1:code>0</ns1:code>
<ns1:message>An internal error has occurred. Please retry your
request.</ns1:message>
</ns1:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Richard Jones
> Is the sandbox even functioning right now for folks? I am getting an
> internal error on:
I'm getting the same error on addCampaign in the sandbox, although
getAllAdWordsCampaigns works. Full request/response below.
Rich.
Sending to SOAP service:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:fn="https://adwords.google.com/api/adwords/v6"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
><soap:Header
><fn:email
>XXX</fn:email
><fn:password
>XXX</fn:password
><fn:developerToken
>XXX++USD</fn:developerToken
><fn:applicationToken
>merjis</fn:applicationToken
><fn:useragent
>Merjis AdWords Toolkit for OCaml (sandbox)</fn:useragent
></soap:Header
><soap:Body
><fn:addCampaign
><fn:campaign
><fn:dailyBudget
>1000000</fn:dailyBudget
><fn:id
>0</fn:id
><fn:name
>Test</fn:name
><fn:networkTargeting
><fn:networkTypes
>GoogleSearch</fn:networkTypes
><fn:networkTypes
>SearchNetwork</fn:networkTypes
><fn:networkTypes
>ContentNetwork</fn:networkTypes
></fn:networkTargeting
><fn:status
>Paused</fn:status
></fn:campaign
></fn:addCampaign
></soap:Body
></soap:Envelope
>
HTTP error code: 500
Error message: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<responseTime soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/adwords/v6">94</responseTime>
<operations soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/adwords/v6">0</operations>
<units soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/adwords/v6">0</units>
<requestId soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/adwords/v6">d8766a7dece4c369a1bfaf5ea5b0fbf1</requestId>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>An internal error has occurred. Please retry your request.</faultstring>
<detail>
<ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/v6">
<ns1:code>0</ns1:code>
<ns1:message>An internal error has occurred. Please retry your request.</ns1:message>
</ns1:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
--
Richard Jones, CTO Merjis Ltd.