Customer-supplied: paste your OWN X/Twitter cookies from a logged-in browser session. Format: 'auth_token=xxx; ct0=yyy'. Get them from DevTools → Application → Cookies → x.com — copy auth_token (HttpOnly) and ct0 into a single semicolon-separated string. Multi-cookie pool supported via ||| separator (e.g. 'auth_token=A; ct0=1|||auth_token=B; ct0=2') for hot-rotation across runs.
REQUIRED for: x-search-scraper, x-hashtag-scraper, x-timeline-scraper, x-follower-scraper, x-following-scraper, x-comment-scraper, x-list-scraper.
Not needed for: x-post-scraper, x-profile-scraper, x-data-extractor.
Important: this actor does NOT include any X/Twitter cookies for customer runs. When a mode requires authentication, you must paste your own cookies into this field. There is no shared cookie pool, no built-in fallback, and no operator-side cookie injection — every authenticated run uses the cookies you provide, attributing the activity to your X account. (Operator daily-tests use the same loginCookies input field, with cookies passed by the daily-test orchestrator.)
Migration note (2026-05-08): the X_LOGIN_COOKIES environment-variable fallback has been removed. Earlier versions of this actor would silently fall back to the env var if loginCookies was empty; that path is closed for the customer-vs-operator cookie boundary.