docs(social): authenticated Scraper Results polling + scrape persistence note (chat#1840)
Contract-first PR for recoupable/chat#1840 — both items. The api PRs implementing this follow and link back here. Merge order: this docs PR → api PRs.
GET /api/apify/runs/{runId} — auth contract (item 1)
Today the endpoint is admin-only, while these docs, the recoup-platform-api-access skill, and customer task prompts all tell account-key agents to poll it (the can-start/can't-read asymmetry in the issue). New contract (decision 2026-07-03, superseding the earlier owner-or-admin draft): any valid API key or Bearer token can poll any run id. Scrape results are public social content and run ids are unguessable; authentication still gates the endpoint so anonymous callers can't use it as a free Apify proxy. No new response codes — 200/400/500 unchanged.
POST /api/socials/{id}/scrape — persistence note (item 2)
One sentence documenting what completed runs persist: profile stats to the social row, and on Instagram/TikTok/X the scraped post URLs (surfaced via Get Artist Posts). TikTok/X post persistence is api#753.
JSON re-validated; targeted edits only.
🤖 Generated with Claude Code
Summary by CodeRabbit
- Documentation
- Clarified API documentation for social endpoints, including authentication requirements for polling runs.
- Added details on what data is saved after a social scrape completes, including persisted profile stats and scraped post URLs for supported platforms.