Send a stuck payment again with a higher network fee
const url = 'https://api.sotirea.com/v1/payments/example/speed-up';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.sotirea.com/v1/payments/example/speed-up \ --header 'Authorization: Bearer <token>'Only a payment that is stuck: one the network has not taken for 15 minutes, or keeps refusing. It is sent again in its own place with a higher fee, paid from your gas pool. Any other payment is refused 409. Answers the payment as it now stands.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The payment’s id, as sending it answered: api:
Responses
Section titled “Responses”Done.
object
object
In the asset’s smallest unit.
How many people must agree before it is sent; 0 when it needs no approval.
The payment’s id: api:
The network or asset is not available right now: a payment waiting cannot be approved or sent until it is. One already sent is still followed to the end.
Payment, asked for by a person or a key; or sweep, sent by one of your sweep rules from a deposit vault into one of your own vaults.
True for the network’s coin and for tokens on Sotirea’s recognised list. Any other token’s symbol is whatever its contract calls itself, so do not trust it by name.
Requested, awaiting_approval, awaiting_gas, signed, sent, confirmed, failed or stuck. New statuses may be added: treat one you do not know as still in progress.
object
Quote it when asking about a request; it is in the X-Request-Id header too.
Example
{ "success": true}default
Section titled “default”Refused or failed, in words a person can act on.
object
object
object
object
Quote it when asking about a request.
Example
{ "success": false}