# request methods You can use `request` to connect to users' wallets, prompt users to share their Bitcoin & Stacks wallet addresses, and sign messages and transactions with their Bitcoin & Stacks addresses. {% hint style="info" %} The `request` method is available as `Wallet.request` from `sats-connect` if you'd like users to [connect to any wallet](/sats-connect/connecting-to-the-wallet/connect-to-other-wallets.md), or as a named export from `@sats-connect/core` if you only need Xverse Wallet support. {% endhint %} ## Available methods `request` gives you access to a set of [JSON RPC 2.0](https://www.jsonrpc.org/specification) methods which follow the [WBIP001](https://wbips.netlify.app/wbips/WBIP001) standard. All available Bitcoin & Stacks methods are detailed in the present documentation:


Connect, fetch accounts & manage permissions	wallet_connect wallet_disconnect getAccount wallet_requestPermissions wallet_getCurrentPermissions wallet_renouncePermissions wallet_getNetwork wallet_changeNetwork wallet_addNetwork [Legacy ⚠️] getAccounts
Bitcoin Methods	getAddresses getBalance signMessage signPsbt sendTransfer ord_getInscriptions & ord_sendInscriptions runes_getBalance & runes_transfer Runes Minting methods Runes Etching methods
🔴 Stacks Methods	stx_getAccounts stx_signMessage stx_signStructuredMessage stx_signMessage stx_transferStx stx_signTransaction stx_callContract stx_deployContract
Spark Methods	spark_getAddress spark_getBalance spark_transfer spark_transferToken spark_signMessage

## Request parameters

Request parameters	Description
`method`	a string representing the RPC method to call
`params`	the params required by the RPC method
`providerId (optional)`	wallet provider id to use for the request

## Response format & error handling Depending on the status property the response will contain either a result or error object.

Property	Description
`status`	success \| error
`result (optional)`	an object containing the result of the RPC request
`error (optional)`	an object containing the error of the RPC request

Error handling for these methods follows the JSON-RPC 2.0 protocol format:

Property	Description
`code`	`RpcErrorCode`
`message`	error message
`data`	any

Error codes ```tsx enum RpcErrorCode { PARSE_ERROR = -32700, // Parse error Invalid JSON INVALID_REQUEST = -32600, // The JSON sent is not a valid Request object. METHOD_NOT_FOUND = -32601, // The method does not exist/is not available. INVALID_PARAMS = -32602, // Invalid method parameter(s) INTERNAL_ERROR = -32603, // Internal JSON-RPC error USER_REJECTION = -32000, // user rejected/canceled the request METHOD_NOT_SUPPORTED = -32001, // method is not supported for the address provided } ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.xverse.app/sats-connect/wallet-methods/request-methods.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.