Lumepay API

List wallets

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://docs.lumepay.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "Lumepay API MCP server": {
    "url": "https://docs.lumepay.com/mcp"
  }
}
Close
GET /api/v1/wallets

Returns wallets belonging to the authenticated API key owner.

Headers

  • X-API-KEY string Required

    Public API key issued from the Lumepay API key management flow.

  • X-API-SECRET string Required

    API secret paired with the public API key.

Query parameters

  • paymentMethodType string

    Optional payment method type filter for fiat wallets.

  • networkName string

    Optional network name filter for crypto wallets.

Responses

  • 200 application/json

    Wallets returned successfully

  • 403 application/json

    Authenticated API key is not allowed to perform this action

    Hide response attributes Show response attributes object
    • code integer(int32)
    • message string
    • httpStatus integer(int32)
    • requestId string
    • timestamp string(date-time)
    • errors array[object]
      Hide errors attributes Show errors attributes object
      • field string
      • message string
  • 500 application/json

    Unexpected server error

    Hide response attributes Show response attributes object
    • code integer(int32)
    • message string
    • httpStatus integer(int32)
    • requestId string
    • timestamp string(date-time)
    • errors array[object]
      Hide errors attributes Show errors attributes object
      • field string
      • message string
  • 401 application/json

    API key authentication failed

    Hide response attributes Show response attributes object
    • code integer(int32)
    • message string
    • httpStatus integer(int32)
    • requestId string
    • timestamp string(date-time)
    • errors array[object]
      Hide errors attributes Show errors attributes object
      • field string
      • message string
  • 400 application/json

    Request validation failed

    Hide response attributes Show response attributes object
    • code integer(int32)
    • message string
    • httpStatus integer(int32)
    • requestId string
    • timestamp string(date-time)
    • errors array[object]
      Hide errors attributes Show errors attributes object
      • field string
      • message string
GET /api/v1/wallets 
curl \
 --request GET 'http://api.example.com/api/v1/wallets' \
 --header "X-API-KEY: string" \
 --header "X-API-SECRET: string"
Response examples (200)
Fiat virtual EFT wallet 
[
  {
    "id": "wal_3Q8M1K",
    "currency": "ZAR",
    "depositDetails": {
      "bankName": "Nedbank",
      "accountName": "Example Customer",
      "accountNumber": "9876543210",
      "accountType": "Current",
      "branchCode": "198765"
    },
    "networkName": null,
    "paymentMethodType": "EFT"
  }
]
Crypto wallet 
[
  {
    "id": "wal_7K9Q2M",
    "currency": "BTC",
    "depositDetails": {
      "address": "bc1qexample...",
      "address_tag": "123456"
    },
    "networkName": "Bitcoin",
    "paymentMethodType": null
  }
]
Response examples (403) 
{
  "errors": [],
  "timestamp": "2026-01-01T00:00:00Z",
  "code": 403,
  "message": "Authenticated API key is not allowed to perform this action",
  "requestId": "req_01HY0000000000000000000000",
  "httpStatus": 403
}
Response examples (500) 
{
  "errors": [],
  "timestamp": "2026-01-01T00:00:00Z",
  "code": 500,
  "message": "Unexpected server error",
  "requestId": "req_01HY0000000000000000000000",
  "httpStatus": 500
}
Response examples (401) 
{
  "errors": [],
  "timestamp": "2026-01-01T00:00:00Z",
  "code": 401,
  "message": "API key authentication failed",
  "requestId": "req_01HY0000000000000000000000",
  "httpStatus": 401
}
Response examples (400) 
{
  "errors": [],
  "timestamp": "2026-01-01T00:00:00Z",
  "code": 400,
  "message": "Request validation failed",
  "requestId": "req_01HY0000000000000000000000",
  "httpStatus": 400
}