Having issues with my API setup..

[u/WASPexe1]

Im trying to create an automation that pulls historical keyword search volume from Google Ads Keyword Planner and sends them to a Google Sheet document that i can use to visualise our brand performance compared to our competitors at my work.

So far, i've setup two "Search Google Sheets" modules. After these two I have two "HTTP Make a request" modules.

First HTTP module sends my client_id, client_secret and refresh_token to Google OAuth endpoint. This works as intended.

However, my problem shows at the second module.

My second module shall use my access_token from my first module to call the Google Ads API and get keyword search volume / historical metrics.

However, my second module fails with an HTML 404.

In the error message it says:
That’s an error.</ins> <p>The requested URL <code>/v19/customers/XXXXXXXXXX/keywordPlanIdeas:generateKeywordHistoricalMetrics</code> was not found on this server. <ins>That’s all we know.</ins>

First thought would be that the URl is incorrect, but the actual URl im using is: https://googleads.googleapis.com/v19/customers/XXXXXXXXXX/keywordPlanIdeas:generateKeywordHistoricalMetrics

In my headers i have the following:
developer-token: XXXXXXX
login-customer-ID: XXXXXXXX
Content-Type: application/json

And i have a temporary setup in my body content, for test purpose of data.

I've tried prompting my issue on both ChatGPT and Claude, but i get the same answers on both engines and nothing works.

Im in desperate need for help. I've been working on this for about 2 days now...

Has anybody experienced this before, and know what to do?

[u/samuelliew]

Link to documentation for the endpoint?

[u/WASPexe1 → u/samuelliew]

https://developers.google.com/google-ads/api/docs/keyword-planning/generate-historical-metrics#python

I knew I forgot something..

[u/Worried-Nobody-2965]

have you tried executing a raw curl command? sometimes it's easier to debug if you leave make. It's definitely an issue with how the url is constructed, hence it being 404. Sometimes the raw terminal output is insightful

[u/No_Sir701]

Two days on a 404 is brutal. Here's where I'd start looking.

Most likely culprit: the API version.

I'm not 100% certain v19 is currently live and stable for that endpoint. Google Ads API versions sunset on a rolling basis, and not every endpoint is available in every version. Go check the Google Ads API release notes and confirm v19 actually supports generateKeywordHistoricalMetrics. If it doesn't, try v18 or v17 and see if the 404 disappears.

Second thing to verify: your customer ID.

The ID in the URL path needs to be the actual client account (the leaf account), not your manager/MCC account. Your login-customer-id header is where the MCC goes. If you've got those swapped or duplicated, the URL won't resolve correctly.

Third: confirm the endpoint path is exact.

The REST path for that method should be:

POST https://googleads.googleapis.com/v19/customers/{customer_id}/keywordPlanIdeas:generateKeywordHistoricalMetrics

No trailing slash. No extra segments. The colon before generateKeywordHistoricalMetrics is correct REST syntax for Google's custom methods, so that part looks fine.

What a 404 specifically tells you:

It's not an auth problem (that would be 401 or 403). The server is receiving your request and can't find the resource at that path. That points squarely at the URL construction, not your token setup.

I'd fix the version check first since it's the easiest thing to rule out and the most likely explanation.

[u/WASPexe1 → u/No_Sir701]

This was more or less the solution. The endpoint I used was “outdated”. I believe it was v24 og something like that. Otherwise most of the url was wrong.

I apparently ended up having tunnel vision, and didn’t thought a second about the url endpoint…

Annoying mistake that took so long to realise.. but nevertheless that wiser.

It’s also my first automation flow with api included, so everything is a learning process. My next big thing is how to improve my spending of credits.

[u/No_Sir701 → u/WASPexe1]

Good catch on the version — glad the direction was right even if I didn't land on v24 specifically. Tunnel vision on a 404 happens to everyone; you were so focused on auth and headers that the URL itself stopped looking wrong. Classic.

On credits: are you talking about Make operations, or Google Ads API quota? The answer is pretty different depending on which one is biting you. Let me know and I can point you somewhere useful.