Admin Diagnostics
Inspect Scout Following Evidence
Inspect stored Scout relationships and recent-window counts for a Twitter account, including accounts absent from Trending.
GET
Inspect Scout Following Evidence
Requires an authenticated admin session (cookie or Bearer session token), not a public API key.
Read-only: does not query Twitter, refresh profiles, or trigger ranking. Returns 403 for non-admin
users and 404 when no evidence is stored. These are observed relationships, not exact Twitter
follow timestamps. Baseline means the follow already existed at first sync; its original time is
unknown. Meeting the Scout minimum alone does not guarantee a Trending position.
Parameters
Twitter user ID or handle, optionally prefixed with @. An explicit @ always selects a handle,
including all-digit handles; bare numeric input selects a Twitter user ID. Handles require a
stored profile; use the numeric ID when the profile is missing.
Response
Stored profile: twitterUserId, handle, displayUsername, displayName, followersCount,
profileRefreshedAt, profileExpiresAt and profileIsStale. Missing profile values are null.
trackedScoutCount, activeScoutCount, inactiveScoutCount, baselineActiveScoutCount,
firstNewFollowDetectedAt, latestNewFollowDetectedAt, latestFollowingSeenAt and latestScoutSyncAt.
Timestamps are ISO 8601 or null.
1h, 3h, 6h, 24h and 7d. Each contains newScoutFollowCount and meetsMinimumScoutCount. Active,
non-baseline relationships observed within the window are counted; the minimum is 2 Scouts.
Each relationship includes scoutAccountId, twitterUserId, handle, displayUsername, displayName,
source, enabled, syncSuspended, lastFollowingSyncAt, lastFollowingSyncStatus,
followingSyncConsecutiveFailures, detectedAt, lastSeenAt, active, isBaseline and
observedInWindows. For baseline rows, detectedAt is a sentinel (2000-01-01), not an actual follow
date. active reflects the latest stored observation, not a live Twitter check.