Skip to main content
Blend exposes two API surfaces from the same backend. They share the same data and schemas but differ in authentication and how they identify the account.

Frontend API

For browser apps. Auth with a publishable key and SIWE wallet signature. The account is implicit from the signed session.

Server API

For backends. Auth with an API key. The account type and account ID are explicit in the URL path.

​
Which one do I use?

Frontend APIServer API
Runs inBrowserYour backend (Node.js, Python, etc.)
AuthX-Publishable-Key + SIWE bearer JWTX-API-Key
Account scopingAutomatic from the signed sessionExplicit via {accountTypeId} and {accountId} in the URL
Auth endpointsYes (/auth/challenge, /auth/verify, /auth/sign-out)No
Account lookupNo (account resolved from JWT)Yes (GET /account?address=...)
SDK@blend-money/fe@blend-money/node
Base URLhttps://api.portal.blend.money/extern/fehttps://api.portal.blend.money/extern/svr/{accountTypeId}
Both surfaces return the same response shapes. A balance response from the frontend API is identical to one from the server API.

​
Common patterns

Every response wraps data in a standard envelope: 
{
  "status": "success",
  "data": { ... }
}
Errors follow the same shape: 
{
  "status": "error",
  "message": "Human-readable error description"
}

Frontend API

Browse all 21 frontend endpoints

Server API

Browse all 19 server endpoints
Last modified on May 29, 2026