Google Trends API: 3 ways to get Trends data by API

You want a Google Trends API that hands your agent interest over time for a few search terms as JSON, one call per query, without a browser and without scraping the Trends page yourself. Google's own API is a limited alpha, so most developers buy Trends data from a search data provider instead.

This post ranks the three providers in the looot catalog that return Google Trends data by API: SearchApi, SerpApi and DataForSEO. You get a comparison table, live prices per call, what each endpoint returns and where it falls short, a guide for choosing, a prompt you can paste into an agent and a FAQ.

Google Trends API: the short answer

Each provider fits a different job. All three bill per call and return JSON.

• SearchApi, best for interest over time plus trending searches and Trends autocomplete from the same vendor: its Google Trends endpoint sits next to three other Trends endpoints in the catalog.
• SerpApi, best for one call that compares several terms: it takes comma-separated queries and returns interest_over_time or another data_type view.
• DataForSEO, best for Trends across Google Search, News, Images, Shopping and YouTube, plus demography and subregion breakdowns inside a large SEO catalog.

Prices are read from the catalog when the page loads, one row per provider.

Key takeaways

• DataForSEO sells two kinds of trend data. Its google_trends endpoint reads Google Trends Explore. Its dataforseo_trends endpoint returns DataForSEO's own popularity data for Search, News and Shopping. Pick the one whose source you want to cite.
• SerpApi passes back its raw JSON, so your agent reads search_metadata.status and the interest_over_time block itself.
• The catalog marks none of these endpoints as verified on 2026-11-04. Run one test call before a batch.

How we ranked these providers

We read the public looot catalog on 2026-11-04 and kept every provider with a Google Trends endpoint that the blog can price. We ordered them by the price per call of each provider's cheapest Trends endpoint, cheapest first. All three bill per call, not per result, so the prices compare directly. The live table above shows today's numbers, and they can change after this post.

The tie-break would have been breadth of related Trends endpoints from the same provider. No tie came up. We did not run these endpoints for this post. The catalog publishes no measured success rate or speed for them, so we rank on neither and quote neither. Google's own alpha API is not ranked, because looot cannot call it.

1. SearchApi, best for Trends plus trending searches

The endpoint search_google-trends from SearchApi returns Google Trends data on search term popularity across time periods, locations and categories. Its catalog description names two jobs: comparing interest over time and spotting trending search topics. SearchApi also lists a Trends autocomplete endpoint and two trending now endpoints, so an agent can find a rising topic, expand it, then chart it, all through one vendor. See the SearchApi page for the full list.

Best for

• Comparing three product names over the past year before you name a feature.
• A content plan that starts from what is trending now and checks each idea's curve.

Strengths

• Several Trends views from one provider, so the agent keeps one response shape.
• Per call billing, so the cost of a run is the number of calls times the live price.

Limits

• The catalog description does not list the response fields. Read one response before you write a parser.
• The endpoint is marked unverified in the catalog on 2026-11-04.

Does not fit someone who needs Trends broken down by age or gender. That is DataForSEO's demography endpoint.

2. SerpApi, best for comparing several terms in one call

The endpoint search_google-trends from SerpApi takes one or more comma-separated queries and returns Google Trends interest_over_time or another data_type view that you pick. The response is raw SerpApi JSON. search_metadata.status reads Success when the search ran. For an agent that compares a short list of terms, one call returns every curve.

Best for

• Charting four competitor brand names against each other in one request.
• Teams that already parse SerpApi JSON for other Google results.

Strengths

• Several terms per call, so one request covers the whole comparison.
• The data_type parameter switches views without a second endpoint.

Limits

• It is the only SerpApi Trends endpoint in the catalog. There is no trending now or autocomplete endpoint from SerpApi here.
• Success means the search ran, not that the terms had enough volume to chart. Check the values.

Does not fit an agent that wants a cleaned, flat response. It gets the vendor's raw JSON.

3. DataForSEO, best for Trends by channel and audience

DataForSEO lists two explore endpoints. keywordsdata_google-trends_explore_live-ai returns keyword popularity from the Explore feature of Google Trends for Google Search, Google News, Google Images, Google Shopping and YouTube. keywordsdata_dataforseo-trends_explore_live-ai returns DataForSEO Trends data, its own popularity numbers, for Google Search, News and Shopping. The catalog also lists DataForSEO Trends demography and subregion interests, plus a Google Trends categories endpoint. The DataForSEO page shows the rest of its SEO catalog.

Best for

• Checking whether a term grows on YouTube while it stalls on web search.
• Pairing a trend curve with keyword volume from the same vendor.

Strengths

• Five Google channels from one Google Trends endpoint.
• Demography and subregion breakdowns that the other two providers do not list.

Limits

• The DataForSEO Trends endpoint is not Google Trends. Its numbers come from DataForSEO, so do not mix the two curves on one chart.
• Both explore endpoints are marked unverified in the catalog on 2026-11-04.

Does not fit a quick one-off curve where the extra channels add nothing.

How to choose

What do you need back?

One curve per term from Google Search: any of the three. Several terms in one request: SerpApi. Curves for YouTube, News, Images or Shopping: DataForSEO's Google Trends endpoint. Trending searches right now: SearchApi.

Do you need a second Trends view?

If the job goes past interest over time, the provider choice narrows. SearchApi adds autocomplete and trending now. DataForSEO adds demography, subregions and categories. SerpApi offers one Trends endpoint here.

How many terms do you check?

All three bill per call, so cost grows with the number of calls. SerpApi's catalog description is the only one that says it takes several comma-separated terms per call, which cuts the count. For the other two, plan one call per term until a test call shows otherwise. Read the live table, then multiply.

Does it need to run on a timer?

A weekly trend report needs scheduled runs, not available yet. Run it by hand from your agent and keep the prompt so each run asks the same thing.

How to run this with an agent

1. Connect your agent to looot once with the setup line in the prompt below.
2. Ask it to search the catalog for "Google Trends interest over time". It lists each endpoint with its inputs and price.
3. Give it three terms and a country, and pick one provider.
4. Read the table it writes. Run a second provider on the same terms if the curve looks wrong.
5. Run the full list with a budget in the prompt.

For the endpoint list behind this post, see the Google Trends API use case or browse the public catalog.

What this post does not cover

It covers priced Google Trends endpoints that an agent calls one query at a time. It does not cover scraping libraries you host yourself or Google's alpha API, which needs an application to Google. It makes no claim about accuracy or speed, because the catalog publishes no measured rate for these endpoints. Providers in the live catalog that are not in the blog's provider snapshot, dated 2026-10-12, are left out until that snapshot is refreshed.

Last checked 2026-11-04 against the public catalog at https://api.looot.ai/v1/public-catalog. Author: the looot team.