---
page_title: Get Wallet
product: API Reference
page_source: https://juspay.io/in/docs/api-reference/docs/express-checkout/get-wallet
openapi: https://juspay.io/in/docs/api/swagger?document=https%3A%2F%2Fjuspay.io%2Fin%2Fdocs%2Fapi-reference%2Fdocs%2Fexpress-checkout%2Fget-wallet
llms_txt: https://juspay.io/in/docs/llms.txt
product_llms_txt: https://juspay.io/in/docs/api-reference/llms.txt
---

## API Version: default


# Get Wallet



Get the wallet details. You can also use this API to generate one-time use token for direct debit transactions. ## Endpoints:
- Sandbox: https://sandbox.juspay.in/wallets/{wallet_id}

- Production: https://api.juspay.in/wallets/{wallet_id}

## Request Type: 
GET

## Authorization:

#### Basic Auth:
Consists of two parts.

* Username: API Key obtained from Juspay dashboard
* Password: Empty string
- Value: Example:- Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
- Tags: Base64 Encoded Username:Password, Mandatory
## Headers:

#### x-routing-id:
We recommend passing the customer_id as the x-routing-id. If the customer is checking out as a guest, you can pass an alternative ID that helps track the payment session lifecycle. For example, this could be an Order ID or Cart ID.

> **Warning**
> This ID is associated with the customer. It plays a key role in ensuring consistency and maintaining connections across different systems. If you fail to pass the same x-routing-id for the same customer in all related API calls, it could lead to issues with API functionality. Therefore, it’s crucial that you use the same x-routing-id for all requests tied to the same customer.


- Value: customer_1122
- Tags: String, Required
## Sample Code Snippets:
### Sample Request:

#### Request Code Snippet:

```request
curl -X GET https://api.juspay.in/wallets/$wallet_id \
-u your_api_key: \
-H 'x-routing-id: customer_1122'

```

### Sample Response:

#### Response:
```json
{
  "id": "wlt_q23xzki3pazgtezo",
  "object": "wallet_account",
  "wallet": "MOBIKWIK",
  "token": "tok_winysteev9eftrwcv6me",
  "current_balance": 250,
  "linked": "true",
  "last_refreshed": "2016-08-02T08:07:52+0000"
}
```

## Path Parameters:

#### wallet_id:
Wallet Id of the wallet
- Tags: String, Mandatory
## API Responses:
### 200:

#### id:
- Description: wlt_q23xzki3pazgtezo
- Tags: string

#### object:
- Description: wallet_account
- Tags: string

#### wallet:
- Description: MOBIKWIK
- Tags: string

#### token:
- Description: tok_winysteev9eftrwcv6me
- Tags: string

#### current_balance:
- Tags: integer

#### linked:
- Description: true
- Tags: string

#### last_refreshed:
- Description: 2016-08-02T08:07:52+0000
- Tags: string
### 400:

#### object:
- Description: {}
- Tags: object



### API Latency Guidelines




#### **What is API Latency?** 



Time taken by the server to respond to the API request.


#### **Average API Percentile Metrics and Recommended Timeout** 



**TP50 (ms)** : This represents the median latency, meaning 50% of all requests are completed in this time or less. It indicates the typical performance experienced by the majority of users.

**TP90 (ms)** : This value shows that 90% of requests are completed within this time, leaving 10% of requests that take longer. It gives insight into the performance for a broader set of users, beyond the median.

**TP99 (ms)** : This value indicates that 99% of requests finish within this time, with only 1% of requests taking longer. It helps identify outlier cases where latency may become an issue for a small group of users.

**TP99.9 (ms)** : This metric captures extreme latency outliers, where only 0.1% of requests take longer than this value. It’s useful for understanding edge cases where performance degrades for very few users.

**TP99.99 (ms)** : This measures the most rare and severe performance outliers, where just 0.01% of requests exceed this time. Monitoring this helps in addressing the rarest and most critical latency issues that may impact user experience in exceptional scenarios.


|  Transaction Percentile |  Latency (ms) |
|---|---|
|  TP50 (ms) | 25.428 |
|  TP90 (ms) | 36.85 |
|  TP99 (ms) | 102 |
|  TP99.9 (ms) | 232.14 |
| Recommended Timeout(ms) | 1000 |


> **Warning**
> The recommended timeouts are based on TP99.9 data, though edge cases (0.01% of requests) may still exceed these limits and are captured in the TP99.99 data as shown below.
> 
> 
> |  Transaction Percentile |  Latency (ms) |
> |---|---|
> |  TP99.99 (ms) | 309.714 |
> | Recommended Timeout(ms) | 1000 |
> 



---

## See Also

- [Delink Wallet](https://juspay.io/in/docs/api-reference/docs/express-checkout/delink-wallet)
- [Refresh Wallet](https://juspay.io/in/docs/api-reference/docs/express-checkout/refresh-wallet)