TikTok user stories

The platform keys this on the numeric user_id; passing unique_id instead costs one extra resolve call. An empty posts list means no live story right now.

Deliberately takes no count: the story surface returns a fixed-size page and ignores every page-size value sent to it (verified live), so accepting a knob that provably does nothing would be dishonest. Page with cursor.

The example response below is real output from this endpoint, not an illustration. Long lists and long strings are shortened to keep the page readable, and each place that happens is marked. This example took 1.3s.

curl -X POST "https://example.com/v1/scrapers/tiktok-user-stories-v4" \  -H "Content-Type: application/json" \  -d '{    "user_id": "107955",    "cursor": "0"  }'

{  "request_id": "req_8f2c1d94e7b0",  "success": true,  "status": {    "code": "OK",    "message": "Scrape completed.",    "retryable": false  },  "data": {    "aweme_list": [],    "cursor": null,    "has_more": false,    "unique_id": null,    "user_id": "107955"  },  "error": null,  "meta": {    "client_id": "client_abc123",    "scraper": "tiktok-user-stories-v4",    "billable": true,    "duration_ms": 737  }}