Authentication
Authorize The CLI With A Browser Approval Flow
The CLI uses a short-lived browser approval flow. The terminal shows a pairing code, the browser shows the same code, and you approve only when both codes match.
Separate access
CLI authorization is separate from browser and extension sign-in. The CLI token is stored in operating system credential storage, while the config file keeps only non-secret account details.
Command
Start Login And Verify The Account
webcull login
webcull whoami
webcull loginStarts authorization and opens the browser approval page.
webcull auth loginAlias for
webcull login.webcull whoamiPrints the authorized account and token expiry.
Output
Read The Account Response
{
"success": "true",
"user": {
"id": 42,
"hash": "abc123abc123abc123abc123abc123",
"email": "[email protected]"
},
"scopes": ["bookmarks:read", "bookmarks:write"],
"expires": 1781300000
}
Use scopes to confirm what this token can do. Read commands require bookmarks:read. Create, update, reminder create, and reminder cancel require bookmarks:write.