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

# Use Para from Your Backend

> Follow this path when your backend owns auth, wallet provisioning, automation, or signing with Para APIs and server-side tools.

Use this path when your backend is the integration boundary. This usually means your server owns user identity, needs to provision wallets programmatically, automates wallet operations, or calls Para from server-side code.

## Choose This Path If

* Your backend owns user authentication or maps existing users to Para wallets.
* You want to create or pregenerate wallets before users visit your app.
* You want HTTP endpoints, cURL, or language-native clients instead of a client SDK.
* You want server-side helpers for sessions, pregeneration, automation, or chain operations.

<Info>
  REST API and Node & Server are related but not identical. REST API is the direct HTTP surface. Node & Server is the SDK path for backend JavaScript integrations.
</Info>

## Integration Lifecycle

<Steps>
  <Step title="Create a Para project">
    Create a project and API key in the [Developer Portal](https://developer.getpara.com/), then review [Developer Portal setup](/v3/general/developer-portal-setup). Protect backend API keys before making requests.
  </Step>

  <Step title="Pick REST API or server SDK">
    Use the [REST API](/v3/rest/overview) for direct HTTP wallet operations. Use [Node & Server](/v3/server/overview) when you want server-side SDK helpers in a JavaScript backend.
  </Step>

  <Step title="Connect users and wallets">
    For REST, start with [REST setup](/v3/rest/setup), [REST SDK](/v3/rest/sdk), [multi-wallet setup](/v3/rest/multi-wallet), or [permissions](/v3/rest/permissions). For server SDK, start with [sessions](/v3/server/guides/sessions) or [pregen](/v3/server/guides/pregen).
  </Step>

  <Step title="Sign from the backend">
    Use the REST endpoints or server SDK chain guides for EVM, Solana, Cosmos, or Stellar signing.
  </Step>

  <Step title="Prepare for launch">
    Review IP restrictions, API key handling, [webhooks](/v3/general/webhooks), the [Go Live Checklist](/v3/general/checklist), and [Production Deployment](/v3/general/production-deployment).
  </Step>
</Steps>

## Next Docs

<CardGroup cols={2}>
  <Card title="REST API" icon="server" href="/v3/rest/overview">
    Create wallets and sign raw bytes from your backend over HTTP.
  </Card>

  <Card title="REST SDK" icon="code" href="/v3/rest/sdk">
    Use the TypeScript client for backend wallet operations.
  </Card>

  <Card title="Node & Server" icon="server" href="/v3/server/overview">
    Use Para's server-side SDK for JavaScript backend integrations.
  </Card>

  <Card title="Server pregen" icon="wallet" href="/v3/server/guides/pregen">
    Create wallets before users sign up or visit your app.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/v3/general/webhooks">
    Subscribe your backend to Para wallet and user events.
  </Card>

  <Card title="Production deployment" icon="rocket" href="/v3/general/production-deployment">
    Move backend integrations from `BETA` to `PRODUCTION`.
  </Card>
</CardGroup>