Authentication requirements
Most Octoparse CLI commands require authentication. An API key or OAuth session identifies your account and authorizes access to your Octoparse tasks and data.Starting with CLI v0.1.33,
template search, template view, and template version require credentials. CLI v0.1.32 allowed these commands to browse the same template catalog without logging in.Login methods
Octoparse CLI supports two login methods: OAuth and API key.OAuth (browser-based)
Open a browser login flow and store access and refresh tokens locally:API key
Create API keys in the Octoparse console:Open API keys page
Create, copy, and manage Octoparse API keys from your account center.
The CLI verifies the API key before saving it. Invalid keys are not stored.
Use an environment variable
For CI or temporary sessions, provide credentials through environment variables instead of stored credentials:Credential precedence
Octoparse CLI checks credentials in this order:octoparse auth login.
On macOS and Linux:
Check and manage auth status
Confirm your session is active:What’s next
Run your first task
List tasks, inspect a task, run it locally, and export data.
Browse all commands
Review authentication, task, local run, cloud run, and export commands.