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

# API Reference

> Complete reference for the dejaVu v1 API

# dejaVu API v1

This section is the technical reference for the dejaVu API v1. Endpoints are documented from the canonical OpenAPI specification.

## Authentication

Most endpoints accept an API key in the `x-api-key` header or a Bearer token in `Authorization`.

```http theme={null}
x-api-key: pk_YOUR_KEY
```

or:

```http theme={null}
Authorization: Bearer YOUR_KEY
```

API keys must not be placed in the URL. The `?api_key=` query-string form is not supported.

## Response conventions

Endpoints using the standard response envelope return an object containing `success` and, depending on the operation, `data`, `pagination`, or `user`.

HTTP status codes are the source of truth for determining whether a request succeeded.

## Interactive API reference

The OpenAPI reference can provide an interactive request builder when enabled by the documentation platform. Use it to inspect the endpoint contract, authentication requirements, parameters, request bodies, and responses.

For advanced dejaVu-specific tests, use the test environments and integration tools intended for your client.

<Warning>
  Never expose an `sk_` key in a client application or publicly distributed
  code.
</Warning>
