Step 6 - Set Up the /api Folder + Magmar Routes
In this step we wire up every server-side call your dApp needs.
You’ll create four HTTP endpoints in /app/api that rely on the Magmar SDK stack.
Endpoint
Purpose
Magmar module
/api/get-signer
Deterministically derive the owner address behind a Smart-Contract Wallet (SCW)
@magmar/aa-core
/api/get-user-nfts
Fetch NFTs owned by an SCW for dashboard display
magmar-nft-sdk
/api/mint-nft-user-op
Send a sponsored UserOperation that mints an NFT to the user’s SCW
@magmar/aa-core + @magmar/aa-paymaster
/api/get-user
Retrieve a user’s encrypted private key from Userbase (demo only)
axios
6.1 Install Magmar Server-Side Dependencies
npm i @magmar/aa-core @magmar/aa-paymaster magmar-nft-sdk axios6.2 Project Structure
/app
/api
/get-signer
route.ts
/get-user-nfts
route.ts
/mint-nft-user-op
route.ts
/get-user
route.ts6.3 /get-signer/route.ts
/get-signer/route.ts6.4 /get-user-nfts/route.ts
/get-user-nfts/route.ts6.5 /mint-nft-user-op/route.ts (sponsored mint)
/mint-nft-user-op/route.ts (sponsored mint)6.6 /get-user/route.ts (demo-only key fetch)
/get-user/route.ts (demo-only key fetch)6.7 Update .env.local
.env.localResult
/sign-upand/loginnow compile without red errorsA new user can register, mint an NFT, and view it all gas-free using Magmar Paymaster sponsorship
PreviousStep 5 – Utility Modules & Environment VariablesNextStep 7 - Set Up Your Home Route for Magmar
Last updated