auth

`wallapop auth`

Import a browser session for the active profile

wallapop auth login [flags]

Import a browser session for the active profile.

Wallapop keeps the durable login in an HttpOnly cookie, so the CLI needs a cookie export from a browser where you are logged in:

Install a cookie export extension (Cookie-Editor works) and open es.wallapop.com.
Export cookies as Netscape/text and save the file, or copy the value of the cookie named __Secure-next-auth.session-token.
Run this command and paste the file path or the value when asked, or pass --cookies FILE / --cookies-stdin.

The CLI starts its bundled Galleton session engine automatically. The engine renews tokens and stores rotated cookies in its encrypted private vault. Nothing else from the export is kept. Google, Apple and Facebook accounts work the same way, since the cookie is what the browser holds after any login method.

wallapop auth login
wallapop auth login --cookies ~/Downloads/es.wallapop.com_cookies.txt --profile work
cat cookies.txt | wallapop auth login --cookies-stdin

Flag	Type	Default	Description
`--cookies`	string	-	path to a Netscape cookie export
`--cookies-stdin`	bool	`false`	read the cookie export from stdin

`wallapop auth logout`

Forget the active profile's session (keeps watches and config)

wallapop auth logout [flags]

Flag	Type	Default	Description
`--yes`	bool	`false`	accepted for symmetry; logout never prompts

`wallapop auth refresh`

Renew the session through the managed engine

wallapop auth refresh

Renew the session through the managed engine.

Galleton owns credential rotation and persistence. A refresh can still fail when Wallapop revokes the session or requires a new browser login. Enable unattended renewal explicitly with "wallapop auth service enable".