Warm device feed
Calibrate a provisioned guest device context toward a niche with organic feed pulls and AppLog telemetry.
- Upstream
/aweme/v1/feed//service/2/app_log/- Access
- Growth and up
- Runs on
- Primitive
- Billing
- Failed calls are free
Authorization & parameters
Your API key. Create one in API keys.
Path parameters
The device ID. For example 7392011847562901234.
Body
Send JSON with content-type: application/json.
Topic or keyword cluster to calibrate toward. For example mechanical keyboards.
Warming window in seconds. For example 45.
Client and egress
Runs locally on the protocol primitive layer with deterministic codec / cryptographic state. See Devices, signing & primitives.
Response
A 200 returns JSON with stable field names. Every response carries x-credits-cost, x-credits-tier and x-credits-remaining.
Response fields
Key top-level and nested fields decoded from the mobile upstream payload:
Current lifecycle or health status.
Isolated device/proxy context identifier in LeanPool or FullPool.
Provisioned mobile device identifier.
Two-letter ISO 3166-1 country code associated with the item or context.
City-level egress or location identifier.
Decoded niche value.
Decoded feed pulls value.
Decoded videos dwelled value.
Decoded applog batches flushed value.
Interest-graph calibration state (cold, warming, calibrated_warm).
Gateway execution or signing latency in milliseconds.
Errors
Errors return a JSON body with a stable code and cost 0 credits. See Errors and retries.