> ## 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.

# APIs Overview

> Magna exposes two API families — the Admin API for private server-to-server integrations, and the Portal API that powers public claim portals.

Magna offers two distinct APIs. They serve different audiences, use different
authentication, and have different availability guarantees — pick the one that
matches your integration.

<CardGroup cols={2}>
  <Card title="Admin API" icon="key" href="/apis/admin/introduction">
    **Private, server-to-server.** Authenticated with a project API key you
    generate in the Magna admin dashboard. Use it to manage allocations, fund
    and claim, index transactions, and read token data from your own backend.
  </Card>

  <Card title="Portal API" icon="globe" href="/apis/portal/overview">
    **Public, browser-facing.** The API that powers Magna claim portals.
    **v1** is fully public; **v2** adds wallet authentication. Browse the live
    reference at [portal-api.magna.so](https://portal-api.magna.so/docs).
  </Card>
</CardGroup>

## Which API should I use?

|                 | Admin API                                                            | Portal API                                             |
| --------------- | -------------------------------------------------------------------- | ------------------------------------------------------ |
| **Audience**    | Your backend / internal tooling                                      | Public claim portal frontends                          |
| **Base URL**    | `https://app.magna.so/api/external/v1`                               | `https://portal-api.magna.so`                          |
| **Auth**        | Project API key (`x-magna-api-token`)                                | v1: none · v2: wallet signature                        |
| **Versioning**  | `v1`                                                                 | `v1` (public) and `v2` (wallet auth)                   |
| **Throughput**  | Lower — built for back-office automation, not high-frequency traffic | Higher — serves end-user portal traffic                |
| **Typical use** | Create/fund allocations, trigger claims, read supply                 | Show a stakeholder their allocation and let them claim |

<Note>
  The two APIs are independent surfaces. An API key issued for the Admin API
  does **not** grant access to the Portal API, and vice versa.
</Note>

## Get started

<CardGroup cols={2}>
  <Card title="Admin API → Authentication" icon="lock" href="/apis/admin/authentication">
    Generate a project API key and send it on every request.
  </Card>

  <Card title="Portal API → Overview" icon="book-open" href="/apis/portal/overview">
    Understand v1 vs v2 and open the interactive reference.
  </Card>
</CardGroup>