google_trends

Get Google Trends Trending Now for a location

Returns what people in one country or region are searching for right now, with no keyword in: the Google Trends Trending Now list for a place and a time window. Each item has rank (Google's relevance position), title, search_volume (the lower bound of Google's bucket, so 50000 means 50K+), increase_percent (Google shows at most 1000), started_at, ended_at and active (still trending when ended_at is null), categories, breakdown (the related searches Google groups into the trend) and up to 3 news articles Google links to it. total counts every trend matching your filters before limit. Narrow with hours, category and status, and reorder with sort; these are the same filters trends.google.com/trending offers. Google publishes no worldwide list, so location is required. A place and window with nothing trending returns 404 at 0 credits; filters that match nothing return an empty list at 0 credits. Typically under 2 seconds; allow 30 seconds for the slow tail. Exact repeats within 5 minutes are served from cache at 0 credits.

get/google_trends/trending

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/google_trends/trending
  • Auth: API key in header x-api-key

Query parameters

locationstring required

Where to read trends. An ISO country code ('DE', 'US', 'KR'), its English name ('Germany'), or an ISO 3166-2 region inside it ('DE-BY', 'US-CA', 'GB-SCT'). Google covers 125 countries and has no worldwide list; a country it does not cover is rejected with a free 400.

hours'4' | '24' | '48' | '168'

Only trends that started in the past 4, 24, 48 or 168 hours (7 days). Defaults to 24.

category'autos_and_vehicles' | 'beauty_and_fashion' | 'business_and_finance' | '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' | 'climate'

Keep trends Google tagged with this category: 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, or travel_and_transportation. These are Trending Now's categories, not the numeric codes /v1/google_trends/explore takes. Defaults to every category.

status'all' | 'active'

active keeps only trends that are still trending. Defaults to all, which also returns trends that have already ended inside the window.

sort'relevance' | 'search_volume' | 'recency' | 'title'

relevance (Google's own order, the default), search_volume (largest first), recency (most recently started first), or title (A to Z).

limitinteger

How many trends to return after filtering and sorting, 1 to 500. Defaults to 100.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "google_trends",
  "endpoint": "/v1/google_trends/trending",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  },
  "pagination": {
    "next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
    "has_more": true,
    "page_size": 30,
    "stopped_at": "known_id"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.