TikTok trending search: 10 or 50 results, both $0.10
A Sume trending-videos search is $0.10 per accepted call whatever the limit. In production the limit runs 1 to 50 with a default of 10. Fields and a curl.

Asking for 50 results costs the same as asking for 10: each accepted trending-videos call reserves and captures $0.10 of Sume usage, and the docs say the same price includes summary_mode: metadata (Trending videos). In production the limit is 1 to 50 and defaults to 10, so request the larger page when you will use it.
Cost per useful row
The call price does not move with the limit, so the cost per returned video falls as the limit rises (assuming the search returns that many matches).
| limit | Price per call | Price per video |
|---|---|---|
| 10 | $0.10 | $0.01 |
| 25 | $0.10 | $0.004 |
| 50 | $0.10 | $0.002 |
A 50-result request
query is required in production, up to 200 characters. platform supports only tiktok today.
curl -X POST https://api.sume.com/v1/trending-videos/search \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platform": "tiktok",
"query": "reusable water bottle",
"window": "this-week",
"limit": 50,
"region": "US"
}'What you get back
The response is ranked public TikTok metadata: watch URLs, optional cover thumbnails, author handles, metrics, relevance scores and optional lightweight summaries. It does not include raw TikTok video CDN URLs, so there is nothing to download from this call.
Caveat on the rebuilt feed
The docs describe a rebuilt browse feed (no-query grid, a limit up to 100, quality filters) that is on for development and off in production until a flag is set. Code against the production contract unless you have confirmed otherwise, and confirm the live price in GET /v1/catalog.
Sources
Related posts
More in Media tools
- Black Friday supercut in Timeline: 12 segments vs auto chunking
Timeline accepts up to 200 video slots. A single strategy is refused above 12 segments (render_strategy_unsafe); auto chunks the render past 12.
- Timeline refuses more than 8 chained fades: countdown cut fix
Sume Timeline 1.0 refuses more than 8 adjacent fades with too_many_chained_transitions. Alternate hard cuts and fades in a 12-clip holiday countdown.
- Timeline audio concat fails on mono plus stereo: channel mismatch
Joining a mono and a stereo file in Sume timeline audio returns audio_parts_channel_mismatch. Detach both as mono, or match layouts first.
- Timeline audio concat or audio.parts: when the $0.01 job is wasted
Joining audio inside one render is free with audio.parts[] (up to 20 slices). The $0.01 concat job pays off only for a reusable file. A decision table.
Written by Sume