Riken ScraperDocs

Migrating from another API

Same paths, parameters and body keys. Change the base URL and the key.

Our TikTok endpoints use the same paths, query parameters and response keys as the TikTok data APIs most teams already call. If your code uses those paths today, you switch by changing two settings.

beforeafter
base URLyour current providerhttps://scraper.riken.me
auth headerx-api-key: <key>x-api-key: <key> (or Authorization: Bearer <key>)
paths/v1/tiktok/profile and the restthe same
body keyssuccess, credits_charged, credits_remaining, route keysthe same
curl -s "https://scraper.riken.me/v1/tiktok/profile?handle=example_creator" \
  -H "x-api-key: $RIKEN_API_KEY"

What behaves differently

  • No cache. Every answer is fetched live. cache_max_age is accepted if it is one of 1d, 3d, 7d, 14d, 30d, and ignored. There are no cached or cached_at keys.
  • trim is accepted and ignored. region is ignored on the profile endpoints. On keyword search, CA searches from Canada only; any other two letters keep the default order, US then Canada. A value that is not two letters is a free 400.
  • No silent fallbacks. A parameter we cannot honour gets 400 unsupported_parameter, free. We never return unfiltered results for a filter we ignore.
  • user_id works only for accounts in our index. Otherwise pass handle.
  • Stable error codes. Every error has an error code you can branch on. See Errors.
  • We send 429 and 503 with Retry-After. See Capacity and Retry-After.
  • Profile videos returns page 1 only during the beta.

Latency

What our own load tests measured. A guide, not a promise.

MCP server

Use the API as tools in Claude, Cursor, VS Code and other agents. Same key, same prices.

On this page

What behaves differently