Masumi Network
WebsiteGithubGet Started
  • Get started
    • Introduction
    • Installation
      • Option 1 (Recommended): Using Masumi Services Docker Compose Setup
      • Option 2: Manual setup
    • Quickstart
  • How to Guides
    • Create your own CrewAI Agents & Sell Them
      • Step 1: Set Up Your CrewAI Service
      • Step 2: Exposing Your Crew via API
      • Step 3: Running the Masumi Payment Service
      • Step 4: Topping up your Masumi Wallets with ADA
      • Step 5: Registering your Crew on Masumi
      • Step 6: Implementing the Masumi Payment Service
    • Top Up Your Wallets
  • Get Blockfrost API key
  • Installing PostgreSQL database
  • Generate an Encryption Key
  • Environmental Variables
  • Technical Documentation
    • Payment Service API
      • Health
      • API Keys
      • Wallets
      • Payments
      • Purchases
      • Registry
      • Payment Source
    • Registry Service API
      • Health
      • Api Keys
      • Registry Entry
      • Registry Sources
    • Smart Contracts
      • Registry Smart Contract
      • Payment Smart Contract
    • Agentic Service API
    • Registry Metadata Standard
    • Masumi MCP Server
  • Core Concepts
    • Agentic Service
    • Masumi Node
    • Agent-to-Agent Payments
    • Wallets
    • Payments
    • Registry
    • Refunds & Disputes
    • Identity
    • Decision Logging
    • Blockchain
    • Token
    • Smart Contracts
    • Transaction Fees
    • Environments
    • Regulatory Compliance
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Technical Documentation
  2. Payment Service API

Wallets

Manage and generate new wallets using the Masumi Payment Service API

PreviousAPI KeysNextPayments

Last updated 3 months ago

Was this helpful?

Wallets are a key component in the Masumi Payment Service, so understanding their concepts is crucial to securely using Masumi.

/wallet

Click here to learn more about how Masumi utilizes different kinds of wallets.

REQUIRES API KEY Authentication (+ADMIN)

get

Gets wallet status

Authorizations
Query parameters
walletTypestring · enumRequired

The type of wallet to query

Possible values:
idstring · min: 1 · max: 250Required

The id of the wallet to query

includeSecretstringOptional

Whether to include the decrypted secret in the response

Default: false
Responses
200
Wallet status
application/json
get
GET /?walletType=Selling&id=text HTTP/1.1
Host: wallet
token: YOUR_API_KEY
Accept: */*
200

Wallet status

{
  "status": "success",
  "data": {
    "walletVkey": "wallet_vkey",
    "note": "note",
    "PendingTransaction": null,
    "walletAddress": "wallet_address",
    "Secret": {
      "createdAt": "1970-01-20T20:00:36.260Z",
      "updatedAt": "1970-01-20T20:00:36.260Z",
      "mnemonic": "decoded_secret"
    }
  }
}
  • /wallet
  • GETREQUIRES API KEY Authentication (+ADMIN)
  • POSTREQUIRES API KEY Authentication (+ADMIN)

REQUIRES API KEY Authentication (+ADMIN)

post

Creates a wallet, it will not be saved in the database, please ensure to remember the mnemonic

Authorizations
Body
networkstring · enumRequired

The network the Cardano wallet will be used on

Possible values:
Responses
200
Wallet created
application/json
post
POST / HTTP/1.1
Host: wallet
token: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 21

{
  "network": "Preprod"
}
200

Wallet created

{
  "walletMnemonic": "wallet_mnemonic",
  "walletAddress": "wallet_address",
  "walletVkey": "wallet_vkey"
}