LabelService | createLabels

38 views
Skip to first unread message

Hemalatha D

unread,
Feb 13, 2024, 12:06:31 AM2/13/24
to Google Ads API and AdWords API Forum
I'm using xml schema to createLabels. but, getting error HTTP Status Code: 500
To createLabel, do we need to enable permission, if yes, could you please enable it from your end.

Networkcode- 133009657
ApplicationName- Nine Digital (Production)

<?xml version="1.0" encoding="UTF-8"?>
<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>
    <ns1:RequestHeader
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0"
 xmlns:ns1=[gamApiVersion]>
    <ns1:networkCode>[networkCode]</ns1:networkCode>
      <ns1:applicationName>[applicationName]</ns1:applicationName>
    </ns1:RequestHeader>
  </soapenv:Header>
   <soapenv:Body>
      <createLabels xmlns=[gamApiVersion]>
         <labels>          
            <name>[labelName]</name>          
            <types>[labelType]</types>
         </labels>
      </createLabels>
   </soapenv:Body>
</soapenv:Envelope>

=====================

Internal : Unexpected error Error during Web API HTTP Request
HTTP Status Code: 500
HTTP Response Content: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><ResponseHeader xmlns="https://www.google.com/apis/ads/publisher/v202311"><requestId>b85bb2d0c1a5f2c3882d45d6c5945011</requestId><responseTime>116</responseTime></ResponseHeader></soap:Header><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>[PermissionError.PERMISSION_DENIED @ ]</faultstring><detail><ApiExceptionFault xmlns="https://www.google.com/apis/ads/publisher/v202311"><message>[PermissionError.PERMISSION_DENIED @ ]</message><errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="PermissionError"><fieldPath></fieldPath><trigger></trigger><errorString>PermissionError.PERMISSION_DENIED</errorString><reason>PERMISSION_DENIED</reason></errors></ApiExceptionFault></detail></soap:Fault></soap:Body></soap:Envelope>

Google Ads API Forum Advisor

unread,
Feb 13, 2024, 2:56:49 AM2/13/24
to lathakri...@gmail.com, adwor...@googlegroups.com
Hi,

Thank you for contacting the Google Ads API support team.

By reviewing your concern, I understand that you are encountering Internal error and Permission denied errors. Could you please confirm whether you are seeing these errors while using Google Ads API? If yes, kindly note Internal Error occurs when something unexpected happens while processing the request. You can refer to the documentation, to know how to handle the Internal Error. When you retry requests, use an exponential backoff policy. For example, if you first pause 5 seconds before the first retry, you could pause 10 seconds after the second and 20 seconds after the third retry. Exponential backoff helps ensure you are not calling the API too many times.

Permission denied error means the user doesn't have permission to access the customer. According to the documentation, if you're accessing the customer please specify the login-customer-id as the manager account ID without hyphens (-). Client libraries have built in support for this.

If the issue still persists, could you please provide us with the complete API logs (request and response with request-id and request header) generated at your end to assist you further.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
 
You can send the details via Reply privately to the author option, or direct private reply to this email.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02rz3WG:ref"

Thanks,
 
Google Logo Google Ads API Team


Reply all
Reply to author
Forward
0 new messages