How It Works
1
You create a user
Call the Create User endpoint with an email address. Mufi creates the user record immediately.
2
Mufi provisions a wallet
A custodial Polkadot wallet is generated asynchronously. The secret is split using Shamir’s Secret Sharing and distributed across isolated custodians — no full secret is ever stored in one place.
3
You activate the user
Call the Activate User endpoint. Once active, the user can hold assets, receive products, and attend events.
4
You interact through the API
Issue products, check balances, register for events — all through standard REST endpoints with your API key.
Base URLs
Authentication
All API endpoints require a Bearer token — your API key from the Mufi Dashboard.API Key Permissions
API keys have one of two permission levels:
Write-only endpoints will return
403 Forbidden if called with a read-only key.
Conventions
Request Format
- All request bodies use JSON with
Content-Type: application/json - V1 endpoints use snake_case for field names
- Prices are decimal strings (e.g.,
"49.99") to avoid floating point issues - Timestamps are Unix seconds (integer)
- IDs are UUIDs (v4)
User Identification
Users can be identified by any of these fields (in priority order):Pagination
List endpoints acceptpage (1-indexed) and limit parameters. Maximum limits vary by endpoint.
Standard Errors
Deep Dive
Authentication
API key management, permission levels, and security best practices.
Security Architecture
How Shamir’s Secret Sharing, VPC isolation, and multi-region custodians protect wallet secrets.
Custodians
How secret parts are distributed, encrypted, and stored across isolated services.
Bring Your Own Wallet
Attach self-managed non-custodial wallets to Mufi accounts.