Hi team,
since 2025-10-07 JST I’m seeing TikAPI calls to /public/posts intermittently return:

{"message":"Empty response from TikTok.","status":"error","statusCode":200}

Symptoms (concise):

• Affects multiple secUid values.

• Occurs on the first page as well (e.g., cursor=0, count=35).

• Response code is 200 but body is treated as empty by TikAPI.

• Same account may succeed on retry, but flakiness persists.

Minimal repro (example):

GET https://api.tikapi.io/public/posts?secUid=MS4wLjABAAAA...&count=35&cursor=0
Headers: X-API-KEY: **** / X-Account-Key: ****
Observed: {"message":"Empty response from TikTok.","status":"error","statusCode":200}

Recent logs (samples):

22:45:46  ... {"message":"Empty response from TikTok.","status":"error","statusCode":200} URL: .../public/posts?...&cursor=0
22:45:54  ... {"message":"Empty response from TikTok.","status":"error","statusCode":200} URL: .../public/posts?...&cursor=0

Requests:

• Can you confirm if there’s a known incident impacting /public/posts returning empty payloads with 200?

• Any temporary workarounds you recommend (retry/backoff/cursor handling)?

• If tracked internally, please share an incident ID / ETA.

Thanks!