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

# Introduction

> Getting started with Socket API integration

Socket's unified API makes same-chain and cross-chain token swaps simple. This page walks you through the integration process and helps you choose the right approach for your app.

## Integration flow

Integrating Socket involves 4 steps:

1. **Get a quote**: Fetch quote and pricing information from `/v3/swap/quote`
2. **Select a route**: Pick the best route from the returned list using `routeTags` or output value
3. **Submit the transaction**: Send `txData.object` from `userAddress` (approve first if `approval` is present)
4. **Monitor status**: Poll `/v3/swap/status` with the `quoteId`

And that's it! Socket handles the rest — routing, bridging, and settlement.

<CardGroup cols={2}>
  <Card title="Swap V3 API Guide" href="/integrate/integration-guides/socket-api">
    Full integration guide for the Socket Swap V3 API
  </Card>

  <Card title="Deposit Addresses" href="/integrate/integration-guides/deposit-addresses">
    Accept deposits from any chain via deposit addresses
  </Card>

  <Card title="Non-EVM swaps" href="/integrate/integration-guides/additional-guides/solana">
    Swap across EVM and Solana
  </Card>

  <Card title="Charging Fees" href="/integrate/integration-guides/additional-guides/charging-fees">
    Monetize your integration with integrator fees
  </Card>
</CardGroup>

## Quick start: Socket Widget

If you want the fastest path to production, the Socket Widget is a drop-in React component that handles the full swap and bridging UX.

```
pnpm install @socket.tech/widget react react-dom viem @tanstack/react-query
```

See the [Socket Widget](/integrate/socket-widget) page for setup instructions.

## API base URL

Use the dedicated production API base URL:

```
https://dedicated-backend.socket.tech
```

For production access, [request API access](/integrate/get-api-access). Use `https://public-backend.socket.tech` for testing — no auth required.