SignTransaction
SignAndSendTransaction is the simplest and most recommended method for sending a transaction. Backpack submits the transaction immediately after signing so it is safer for users and a simpler API for developers, rather than relying on the application to do so.
However, it is also possible for an app to request just the signature from Backpack. Once signed, an app can submit the transaction itself using the web3.js sendRawTransaction
.
Base URL
Query String Parameters
dapp_encryption_public_key
(required): The original encryption public key used from the app side for an existing Connect session.nonce
(required): A nonce used for encrypting the request, encoded in base58.redirect_link
(required): The URI where Backpack should redirect the user upon completion. Please review Specifying Redirects for more details. URL-encoded.payload
(required): An encrypted JSON string with the following fields:transaction
(required): The transaction that Backpack will sign is serialized and encoded in base58.session
(required): The session token received from the Connect method. Please see Handling Sessions for more details.
Returns
Approve
nonce
: A nonce used for encrypting the response, encoded in base58.data
: An encrypted JSON string. Refer to Encryption to learn how apps can decryptdata
using a shared secret. Encrypted bytes are encoded in base58.transaction
: The signed and serialized transaction that is encoded in base58. Backpack will not submit this transaction. An application can submit this transaction via the web3.jssendRawTransaction
.
Reject
An errorCode
and errorMessage
as query parameters.
Please refer to Errors for a full list of possible error codes.
Last updated