API-key reference
Read one research thread
Read one active Research thread and the counts that describe its current collection. Use it when a product already has the encrypted thread token and needs a focused view rather than the full portfolio page.
GET
/ api/ v1/ research/ threads/ {encrypted_id}API keyAPI key with research:read
Required boundary headers
x-api-key or Authorization: BearerWhat this route does
Use this route when a caller already knows the encrypted thread token and needs the current thread-level status, counts, or favorite projection.
Request and response
Example request
bash
curl "https://vidbyte-backend.onrender.com/api/v1/research/threads/3f2504e0-4f89-41d3-9a0c-0305e82c3301" \
-H "x-api-key: $VIDBYTE_API_KEY"Example response
JSON
{
"encrypted_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301",
"thread_id": "rth_...",
"title": "AI tutoring evidence",
"run_count": 2,
"source_count": 12,
"artifact_count": 8,
"latest_run_id": "rrun_example",
"latest_run_status": "completed",
"latest_run_phase": "completed",
"favorite": false,
"favorited_at": null,
"created_at": "2026-08-10T10:00:00Z",
"updated_at": "2026-08-10T12:00:00Z"
}Response and errors
- Returns the typed thread detail projection and rollup counters.
- Owner IDs, artifact ids, and source bodies are never returned; thread_id is the internal rth_ id, which no route accepts.