REACT_APP_WALLETS_API_BASE_URL (falls back to REACT_APP_ORGANIZATIONS_API_BASE_URL).
All requests require Api-Key and Authorization: Bearer <token> headers.
List Wallets
Filter by entity type:
user, organization, project.Array of wallet objects.
Get Wallet
?cache_bust=<timestamp> to force a fresh fetch.
The wallet’s unique address hash.
Create Entity Wallet
The owning entity type:
user, organization, or project.The unique ID of the owning entity.
A human-readable name for the wallet owner.
The wallet purpose. Common values:
operating (organizations), project_funds (projects), general. Defaults to general.The currency type. Defaults to
CREDITS.Optional metadata. For project wallets, include
{ "organization_id": "<id>" }.Update Wallet
entity_name and description.
The wallet’s unique address hash.
Object containing the fields to update.
Transaction History
The wallet’s unique address hash.
Page number. Defaults to
1.Items per page. Defaults to
20.Array of transaction objects.
Current page number.
Items per page.
Total number of transactions.
Transact (Universal Transfer / Conversion)
from_wallet and to_wallet are the same address, the operation is treated as a conversion.
Source wallet address hash.
Destination wallet address hash. Set equal to
from_wallet for an in-wallet conversion.Asset type to debit from the source wallet (e.g.,
CREDITS).Asset type to credit to the destination wallet. Set equal to
from_asset for a same-asset transfer.The amount to transfer or convert. Must be a number (not a string).
Human-readable description of the transaction.
Additional metadata.
Debit Wallet
The wallet’s unique address hash.
The amount to debit.
Human-readable description of the debit.
Optional external reference ID for idempotency.
Credit Wallet
Admin-Access header).
The wallet’s unique address hash.
The amount to credit.
Human-readable description of the credit.
Optional external reference ID.
This endpoint requires the
Admin-Access header with a valid admin access token.Wallet Transfers
Wallet transfers are a two-step process: the sender creates a transfer request, and the recipient accepts it. Both steps require verification codes.List Transfer Requests
Page number. Defaults to
1.Items per page. Defaults to
20.Create Transfer Request
Transfer details object.
List Pending Transfers
Verify Transfer Sender
The transfer ID.
The sender’s verification code.
Accept Transfer
The transfer ID.
The recipient’s verification code.
Reject Transfer
The transfer ID.