curl --request POST \
--url https://api.example.com/api/v1/wallet/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"destination": "<string>",
"amount_sat": 1,
"comment": "<string>"
}
'{
"message": "<string>"
}Sends an Ark or Lightning payment to the specified destination. Accepts an Ark address, BOLT11 invoice, BOLT12 offer, or Lightning address. Ark address payments are settled instantly via an out-of-round (arkoor) transaction. The amount_sat field is required for Ark addresses and Lightning addresses but optional for invoices and offers that already encode an amount. Comments are only supported for Lightning addresses. To send to an on-chain bitcoin address, use send-onchain instead.
curl --request POST \
--url https://api.example.com/api/v1/wallet/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"destination": "<string>",
"amount_sat": 1,
"comment": "<string>"
}
'{
"message": "<string>"
}Documentation Index
Fetch the complete documentation index at: https://second.tech/docs/llms.txt
Use this file to discover all available pages before exploring further.
Base64url-encoded auth token
The destination can be an Ark address, a BOLT11-invoice, LNURL or a lightning address
The amount to send (in satoshis). Optional for bolt11 invoices. Depending on the
destination, the wallet must contain this amount plus any fees configured by the server in
FeeSchedule [blocked].
x >= 0An optional comment, only supported when paying to lightning addresses
Payment sent successfully
Success message
Was this page helpful?