# VxCloud Documentation

> Multi-cloud DevOps platform by prodxcloud — provision and deploy VMs,
> Kubernetes, databases, serverless and CI/CD across AWS, GCP and Azure
> via a single REST API, the vxcli CLI, or the Python / TypeScript / Go SDKs.

Auth: send `X-API-Key: <token>` (generate via POST /api/v2/setup/api-token).
Test tokens are prefixed `xc_test_*` (sandbox, unbilled); live tokens `xc_live_*`.

## Start Here

- [Overview](https://vxcloud.io/docs): What VxCloud is and how the docs are organized.
- [Getting Started](https://vxcloud.io/docs/getting-started): Account, credentials, first VM and deploy — in curl, Python, TypeScript or Go.

## Build

- [API Reference](https://vxcloud.io/docs/api): 80+ REST endpoints with request/response examples.
- [CLI Reference](https://vxcloud.io/docs/cli): Every vxcli command, grouped by namespace.
- [SDKs](https://vxcloud.io/docs/sdks): Python, TypeScript, Go SDKs + Terraform provider.

## Learn

- [Guides](https://vxcloud.io/docs/guides): Step-by-step deployment tutorials.
- [Integrations](https://vxcloud.io/docs/integrations): GitHub, Slack, Vault, Datadog and 20+ more.

## SalesShift

- [SalesShift](https://vxcloud.io/docs/salesshift): The sales product running on VxCloud — BYOK sending, the leads pool, and what vxcli and the SDKs reach.

SalesShift is a sales product (CRM, sequences, prospect pool, quotes,
e-signed contracts, invoicing, messaging) served by the same control plane
and the same credential as the rest of the platform, under /api/v1/salesshift
and /api/v1/messaging. Providers are bring-your-own-key: mailbox, AI and
payment credentials are stored in the workspace Vault, and Postgres holds
only metadata. Note: the API host runs with openapi_url=None, so
/openapi.json and /docs return 404 there — do not point a generator at them.

- [SalesShift (vxcli salesshift)](https://vxcloud.io/docs/cli/salesshift-vxcli-salesshift): tracked email, dashboard stats, tenant node worker health, the leads pool and saved searches. Deals, sequences, quotes, contracts, invoices, calendar, deliverability and messaging have no command — use the REST API
- [SDK coverage](https://vxcloud.io/docs/sdks): the salesshift module in the Python, TypeScript and Go SDKs covers email plus the leads pool only — 20 of 306 SalesShift routes, and none of the 57 messaging routes

### SalesShift guides

- [Send your first tracked email with SalesShift](https://vxcloud.io/docs/guides/send-first-tracked-email-salesshift): Connect your own mailbox, confirm the tenant node email worker is healthy, send one tracked email, and read the engagement back. Covers the suppression gate and why a pool address is not a real address.
- [Set up a sending pool and protect deliverability](https://vxcloud.io/docs/guides/salesshift-sending-pool-deliverability): Put several mailboxes behind one rotation, set caps and a warmup ramp, verify SPF/DKIM/DMARC, and run an inbox-placement test against a seed list you control. Rotation ships OFF for a reason.
- [Take a deal from lead to signed contract to paid invoice](https://vxcloud.io/docs/guides/salesshift-lead-to-contract-to-invoice): The full quote-to-cash path: reveal and convert a prospect, open a deal, price it from the product catalogue, send a quote that freezes into an e-signable contract, then invoice it and take payment through Stripe or record it manually.

## Optional

- [API Reference](https://vxcloud.io/docs/api): full endpoint catalogue with request/response bodies
- [CLI Reference](https://vxcloud.io/docs/cli): every vxcli command and flag