# Introduction (/docs/sdks)





Paperful SDKs provide a typed, developer-friendly interface for interacting with the [API](/docs/api).

Use an SDK to upload documents, retrieve structured content, search papers, manage resources, and integrate Paperful into your application without working directly with raw HTTP requests.

## Available SDKs [#available-sdks]

<Cards>
  <Card icon="<IconBrandJavascript className=&#x22;size-4&#x22; />" href="/docs/sdks/javascript" title="JavaScript & TypeScript">
    Build with Paperful in Node.js, Bun, serverless environments, and modern TypeScript applications.
  </Card>

  <Card icon="<IconLineDatabase className=&#x22;size-4&#x22; />" href="/docs/api" title="API Reference">
    Explore the underlying REST API used by every Paperful SDK.
  </Card>
</Cards>

## Authentication [#authentication]

All SDKs authenticate against the same [API](/docs/api).

We recommend storing your [API key](/docs/platform/api-keys) in the `PAPERFUL_API_KEY` environment variable:

```bash title=".env"
PAPERFUL_API_KEY="pf_..."
```

<Callout type="warn">
  Never commit API keys to source control or expose them in client-side applications.
</Callout>

## SDK or REST API? [#sdk-or-rest-api]

SDKs are wrappers around the [Paperful REST API](/docs/api).

Use an SDK when you want:

* Typed request and response objects
* Convenient file uploads
* Consistent error handling
* Less HTTP boilerplate
* Better editor autocomplete

Use the [REST API](/docs/api) directly when you are working in an unsupported language or need complete control over HTTP requests.

## More SDKs [#more-sdks]

Paperful's SDKs are built around the same [API primitives](/docs/api), making it straightforward to support additional languages over time.

If your language is not supported yet, you can use the [REST API](/docs/api) directly.
