NAVNavbar
Logo
php python csharp java

Google Trends API: Overview

Google Trends API employs the eponymous Google service to supply you with the following data:
 

  • Keyword popularity rate over time – relative to the highest rate for the specified time period.
  • Location-specific keyword popularity rate – relative to the highest rate for the specified region.
  • Related topics – users searching for the specified keyword also searched for these topics.
  • Related queries – users searching for the specified keyword also searched for these keywords.

 
Specifying two or more keywords, you can compare their popularity rates on a relative scale. However, note that the number of keywords you can compare is limited to five.

For now, Google Trends API provides data based on the ‘Explore’ feature of Google Trends only. However, we plan to expand the number of datasources in the nearest future.
‌ 

Methods

‌ 
Google Trends API supports both Standard and Live methods of data retrieval. If your system requires delivering instant results, the Live method is the best solution for you. Unlike the Standard method, this method doesn’t require making separate POST and GET requests to the corresponding endpoints.

If you don’t need to receive data in real-time, you can use the Standard method of data retrieval. The Standard method requires making separate POST and GET requests. Using this method, you can retrieve the results after our system collects them.

‌Alternatively, you can specify pingback_url or postback_url when setting a task, and we will notify you on completion of tasks or send them to you respectively.

If you need to set several tasks, you can receive the list of id for all completed tasks using ‘Tasks Ready’ endpoint, and then collect the results of each separate task using ‘Task GET’ endpoint.

You can send up to 2000 API calls per minute. Contact us if you would like to raise the limit.
‌ 

Cost

‌ 
The cost can be calculated on the Pricing page.

You can check your spending in your account dashboard or by making a separate call to the User Data endpoint.