> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.lumenia.net/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.lumenia.net/_mcp/server.

# Partner

A **partner** is your company: the top of the hierarchy and the owner of everything you access through the API. It is the principal the API authenticates as.

```
Partner  (your company)      ← your API key
└── Account  (a customer)
    └── Organization
        └── Workspace
```

Everything else — accounts, organizations, workspaces, documents, tools — ultimately belongs to you, the partner.

## The API key *is* the partner

You never pass a partner identifier. Instead, your **API key represents the partner**: authenticating with the key tells the API which partner you are, and every request is automatically confined to the accounts your company owns.

```bash
curl "https://app.lumenia.net/api/v1/me" \
  -H "Authorization: Bearer $API_KEY"
```

```json
{ "partner": { "name": "Acme Partner", "createdAt": "2026-06-15T05:24:00.000Z" } }
```

`GET /v1/me` is the one endpoint that speaks about the partner directly — it verifies the key and returns the partner it belongs to. (Pass `X-Account-Id` as well to also confirm an account is yours; see [Authentication](/documentation/get-started/authentication).)

> **Info**
>
> Each API key is tied to a single partner. If you are issued several keys for the same partner, they behave identically.

## What the partner owns

* **Accounts** — one per customer. The partner can have many; you select which one a request targets with the `X-Account-Id` header. See [Accounts](/documentation/core-concepts/accounts).
* Through those accounts, all **organizations**, **workspaces**, **documents**, and **tools**.

The partner's internal identity is never exposed beyond its `name` and `createdAt`, and there is no partner create/update/delete in the API — a partner (and its keys) is provisioned for you by a LumenOne superadmin. See [Authentication](/documentation/get-started/authentication) for how to obtain and handle keys.