> ## Documentation Index
> Fetch the complete documentation index at: https://docs.privataswap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Privata Wallet API

> Integrate a 50+ provider swap aggregator into your wallet in a single REST surface.

<Note>
  Privata is a non-custodial aggregator. We never custody user funds — deposit addresses
  belong to the executing provider. KYT and AML obligations stay on the licensed
  provider side.
</Note>

## What you get

* **50+ swap providers** behind one REST API (Exolix, ChangeNOW, FixedFloat, SimpleSwap, Godex, Trocador and 44 more).
* **camelCase SDK** for JS/TS (`@privata/wallet-api`) and a wire-compatible **ChangeNOW-style** layer for legacy wallet plugins.
* **SSE event stream** with resumable `Last-Event-ID` plus signed webhooks for partners that prefer push.
* **Programmatic refunds** on 5 providers, ticket-based on the rest, with capability flags surfaced per order.
* **Sandbox** isolated from production payouts. Use `pk_test_...` keys.

## Pick your path

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/guides/quickstart">
    Five-minute order creation flow with the JS SDK.
  </Card>

  <Card title="API Reference" icon="terminal" href="/api-reference/openapi">
    Every endpoint with a live "Try it" playground.
  </Card>

  <Card title="Order lifecycle" icon="diagram-project" href="/guides/order-lifecycle">
    States, transitions and what each one means.
  </Card>

  <Card title="Refund flow" icon="rotate-left" href="/guides/refund-flow">
    How `refund_required` resolves and what UX to ship.
  </Card>
</CardGroup>

## Base URLs

| Surface              | URL                                       |
| -------------------- | ----------------------------------------- |
| Native v1            | `https://api.privataswap.com/partner/v1`  |
| ChangeNOW-compatible | `https://api.privataswap.com/v2/exchange` |
| Status page          | `https://status.privataswap.com`          |

## Versioning

We version at the URL path (`/partner/v1`). Breaking changes get a new path
(`/partner/v2`). Non-breaking additions land in the same path and are
announced in the [changelog](/guides/changelog).
