Admin API
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.
Portal API
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.
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 |
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.
Get started
Admin API → Authentication
Generate a project API key and send it on every request.
Portal API → Overview
Understand v1 vs v2 and open the interactive reference.