prism

What is rising in one country today, with no keyword in: breakout TikTok posts, sounds, hashtags, and Google searches.

Pass country_code (an ISO code Google Trends covers, such as DE). The board is computed live for this call and nothing is stored between calls, so there is no history and no days parameter: repeat calls within 15 minutes are served from cache. breakout_posts are videos on TikTok's local feed for that country, registered there, whose views are at least 3 times the median of the author's own recent posts (pinned posts and posts under 48 hours are left out, at least 8 posts are compared, and rows without enough posts are counted, not shown). rising_sounds are the sounds used most on that feed, with how many of each sound's first page of videos are from the last 3 days and whether it is a returning or new sound. rising_hashtags are TikTok's own hashtag board for the country, with growth from its daily popularity curve and the first day in the window it was non-zero. rising_searches are Google Trends Trending Now, where Google's own start time is the first-seen date. sources and unavailable say which parts answered. TikTok's hashtag board covers 27 markets; elsewhere that section is empty and says why. No language model is used. Music charts and Pinterest Trends are not included yet. The price is provisional.

get/prism/trend-board

Request

Base URL: https://www.socialcrawl.dev/v1
URL: https://www.socialcrawl.dev/v1/prism/trend-board
Auth: API key in header x-api-key

Query parameters

country_codestring required

ISO 3166-1 alpha-2 country code, such as DE, US or KR. Any country Google Trends Trending Now covers.

period'7' | '30'

7 (default) or 30. The window of TikTok's hashtag board. Google Trending Now is always read over its longest window, 7 days.

limitinteger

Rows per section, 1 to 10. Default 10.

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": "prism",
  "endpoint": "/v1/prism/trend-board",
  "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"
    }
  }
}

Changes

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