What's the rule on API connectors

[Navah Hopkins]

Trying to assess if Tray.io is viable to use with Google Ads API (https://tray.io/connectors/google-ads-integrations). Are connectors acceptable or do they fall under third-party data?

[Google Ads API Forum Advisor Prod]

Hi Navah,

Unfortunately, we are unfamiliar with how this tool works. I see from the first link that you provided that Tray.io provides support. I would advise reaching out to them and see if they can help you with the integration.

Regards,
Anthony

Anthony Google Ads API Team

ref:_00D1U1174p._5004Q2FYdqD:ref

[Navah Hopkins]

Thanks! My question is more around confirming that by using them (or a similar tool to house our API credentials) that we aren't putting ourselves at risk for our token being revoked. Can you confirm whether connectors fall under third party (and would not be acceptable) or whether they are seen as they are (a utility to help manage apis)?

Thanks!

[Google Ads API Forum Advisor Prod]

Hi Navah,

Thanks for the clarification. I'll need to take a closer look and see. I'll update you on this thread as soon as I find out.

[Google Ads API Forum Advisor Prod]

Hi Navah,

Please reach out to the compliance team through this form. They should be able to provide insight on this.

[Navah Hopkins]

So coincidentally, we're now getting this error:

{Message:soap:Server: [QuotaCheckError.INVALID_TOKEN_HEADER @ ]: {"ApiExceptionFault":{"message":"[QuotaCheckError.INVALID_TOKEN_HEADER @ ]","ApplicationException.Type":"ApiException","errors":{"attributes":{"xsi:type":"ns2:QuotaCheckError"},"fieldPath":null,"trigger":null,"errorString":"QuotaCheckError.INVALID_TOKEN_HEADER","ApiError.Type":"QuotaCheckError","reason":"INVALID_TOKEN_HEADER"}}}}

Can you provide context into what this means? 

[Google Ads API Forum Advisor Prod]

Hi Navah,

I work with Anthony and let me provide support to your concern.

The INVALID_TOKEN_HEADER error occurs when the developer token in the request is missing or invalid.

The common cause of this issue are:

• The developer token is not set on the request or it contains a typo.
• The namespace of the headers in the request is not correct.

With this, you need to follow the suggestion below:

• Ensure that a developer token has been set and matches the value in the AdWords API Center.
• Ensure that the headers of the request are in the namespace https://adwords.google.com/api/adwords/cm/{version}, where {version} is replaced with the version of the API being used.

However, since you are using a third-party tool, then I would suggest to reach out to the support of that third-party tool. You can clarify to them the set up of your developer token to this third-party tool and you can provide the suggestion I provided earlier as it will help on fixing the issue.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2FYdqD:ref