POST /api/google/trends/trending
Price: 20 credits
Trending searches on Google Trends for a country or subregion over the past 4, 24, 48 hours or 7 days: the query, when it started and ended trending, its search volume bucket, percent increase, related queries and categories. Filter by category and by searches still trending; sort by relevance, search volume, recency or title.
What people are searching for right now in a country or region. search_count is the lower bound of the volume bucket shown on the site (e.g. 5000 for 5K+).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)geo string — Country or subregion code (default: "US"; examples: "US", "GB", "US-CA"; pattern: ^[A-Za-z]{2}(-[A-Za-z0-9]{1,3})?$)hours string — How far back the trending searches started, in hours (default: "24"; one of: "4", "24", "48", "168")category string nullable — Trending category (one of: "autos_and_vehicles", "beauty_and_fashion", "business_and_finance", "climate", "entertainment", "food_and_drink", "games", "health", "hobbies_and_leisure", "jobs_and_education", "law_and_government", "other", "pets_and_animals", "politics", "science", "shopping", "sports", "technology", "travel_and_transportation")is_active boolean — Return only searches that are still trending (default: false)sort string — Order of the results (default: "relevance"; one of: "relevance", "search_volume", "recency", "title")count integer required — Max number of results (min: 1)@type string (default: "GoogleTrendsTrendingSearch")query string requiredgeo string requiredstarted_at integer nullableended_at integer nullableis_active boolean requiredsearch_count integer nullableincrease_percent number nullablerelated_queries array (default: [])categories array (default: [])category_ids array (default: [])web_url string required422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.