API Reference
Provider Guide

X (formerly Twitter) authorization

X supports session import. Import an existing authorized session through the standard authentication flow.

session

X session import: provide an existing authorized session and complete the standard import flow.

  1. 1. Prepare an existing authorized session export before starting the import.
  2. 2. POST /v1/accounts with provider=twitter, auth_mode=session.
  3. 3. POST /v1/accounts/{account_id}/auth/session with params.session_url. Add params.pin if the export is 2FA-protected (default 0000). Persistent routing uses the account-level proxy field; params.proxy_config is only an action-level compatibility override.
  4. 4. POST /v1/accounts/{account_id}/runtime/start after the import succeeds.
  • params.session_urlURL or reference for an existing X session export.
  • params.pinPIN protecting the session export. Defaults to "0000" if the account does not use 2FA.
  • params.proxy_configOptional action-level proxy_config compatibility override. Use the account-level proxy field for persistent routing.

Notes

  • Treat imported session material as a high-value secret and never write it to logs.
  • If the export is not protected by 2FA, the PIN must be the literal string "0000".
  • There is no QR or code flow for X. The .session file is the only supported authentication artifact.