SalesShift (vxcli salesshift)
The SalesShift product surface: tracked email, dashboard stats, the tenant node email worker, and the global prospect pool. Aliases: `vxcli ss`, `vxcli sales`. Auth is whatever `vxcli auth login` stored — an `Authorization: Bearer <jwt>` when an access token is present, otherwise `X-API-Key` — so there is nothing extra to configure. Every leads command honours `--output text|json|yaml`; email, stats and worker always print text. HTTP timeout is 90s. Twenty-one of the entries below are commands; the last three are reference notes covering the shared `--output` flag, exit codes, and what to do when the group is missing. Between them they reach 21 of SalesShift's 363 API operations — deals, sequences, quotes, contracts, invoices, calendar, deliverability and messaging have no command, so use the REST API for those.
24 commands in this section.
SalesShift (vxcli salesshift)
The SalesShift product surface: tracked email, dashboard stats, the tenant node email worker, and the global prospect pool. Aliases: `vxcli ss`, `vxcli sales`. Auth is whatever `vxcli auth login` stored — an `Authorization: Bearer <jwt>` when an access token is present, otherwise `X-API-Key` — so there is nothing extra to configure. Every leads command honours `--output text|json|yaml`; email, stats and worker always print text. HTTP timeout is 90s. Twenty-one of the entries below are commands; the last three are reference notes covering the shared `--output` flag, exit codes, and what to do when the group is missing. Between them they reach 21 of SalesShift's 363 API operations — deals, sequences, quotes, contracts, invoices, calendar, deliverability and messaging have no command, so use the REST API for those.
Was this page helpful?