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

# Portal API

> The public API that powers Magna claim portals. v1 is fully public; v2 adds wallet authentication. Browse the full endpoint reference in the API Reference section.

The **Portal API** is the public, browser-facing API behind Magna claim
portals. It serves the data a stakeholder needs to view and claim their
allocation directly from a portal frontend — without any project API key.

## Base URL

```
https://portal-api.magna.so
```

## Versions

The Portal API ships in two versions that run side by side.

<CardGroup cols={2}>
  <Card title="v1 — fully public" icon="globe">
    No authentication. Read-only portal data (allocations, claim parameters,
    portal configuration) intended to be safe for public consumption.
  </Card>

  <Card title="v2 — wallet authenticated" icon="wallet">
    Adds wallet authentication: the caller proves wallet ownership via a signed
    nonce (sign-in) before accessing wallet-scoped data and actions.
  </Card>
</CardGroup>

|                 | v1                              | v2                                               |
| --------------- | ------------------------------- | ------------------------------------------------ |
| **Auth**        | None (fully public)             | Wallet signature (sign-in with a signed nonce)   |
| **Scope**       | Public, read-only portal data   | Wallet-scoped data and actions                   |
| **When to use** | Rendering public portal content | Anything tied to a specific authenticated wallet |

<Note>
  The endpoint pages in the **API Reference** section are generated from the
  Portal API's live OpenAPI spec, so paths, parameters, and response schemas for
  both versions stay in sync with the running service automatically.
</Note>

## How it differs from the Admin API

The Portal API is **public** and powers end-user portals. To manage allocations,
funding, and other back-office operations from your own systems, use the
private, API-key-authenticated [Admin API](/apis/admin/introduction) instead.
See the [APIs overview](/apis/overview) for a side-by-side comparison.