---
updatedAt: 2025-11-19T15:03:28.000Z
agentTools:
  projectIndex: https://partner.wirexpaychain.com/llms.txt
---

# Get requested erc withdrawals

Retrieves requested erc withdrawals for provided account address

# OpenAPI definition

```json
{
  "openapi": "3.0.1",
  "info": {
    "title": "Wirex BaaS API",
    "description": "The **Wirex BaaS API** enables partners to deliver non-custodial financial services directly to their retail users. Through a single integration, partners can onboard users, verify identities, issue smart wallet–linked cards, and enable crypto-backed bank transfers—without ever handling fiat or taking custody of user funds.</br>All transactions are powered by **user-owned smart wallets**, ensuring security, transparency, and full user control. Wirex acts as the infrastructure provider, so you can focus on building exceptional user experiences while we handle the heavy lifting.",
    "contact": {
      "name": "API Support Team",
      "email": "company@wirexpaychain.com"
    },
    "version": "1.0"
  },
  "servers": [
    {
      "url": "https://api-baas.wirexapp.tech",
      "description": "Sandbox environment"
    },
    {
      "url": "https://api-baas.wirexapp.com",
      "description": "Production environment"
    }
  ],
  "tags": [
    {
      "name": "Activity Feed",
      "description": "The **Activity Feed APIs** enable partners to access a detailed, chronological view of a retail user's actions within the platform. These APIs provide transparency into key transactional and operational events, helping partners deliver real-time insights and enhanced user experiences.\n\n### Key Features:\n\n- **Comprehensive Activity Tracking**:\n    - Access a full history of user activity, including payments, transfers, and operational events.\n    - Ensure transparency across key user interactions with the platform.\n\n- **Event Filtering & Categorization**:\n    - Filter activities by action type (e.g., card payment, bank transfer) and activity subject (e.g., card, account).\n    - Enable tailored views of user behavior for reporting or support use cases.\n\n- **Chronological Feed Structure**:\n    - Events are presented in a time-ordered format for clear activity timelines.\n    - Easily integrate with user dashboards or support tools.\n\n- **Real-Time Synchronization**:\n    - Designed for near real-time updates to reflect the most recent user actions.\n    - Ideal for monitoring recent transactions or building dynamic activity interfaces.\n\n---\n\nWith the Activity Feed APIs, partners gain a powerful tool to monitor user behavior, enhance visibility into platform usage, and build features that promote trust, engagement, and support responsiveness."
    }
  ],
  "paths": {
    "/api/v1/withdrawal/requests": {
      "get": {
        "tags": [
          "Activity Feed"
        ],
        "summary": "Get requested erc withdrawals",
        "description": "Retrieves requested erc withdrawals for provided account address",
        "responses": {
          "200": {
            "description": "OK",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/response.RequestedErcWithdrawalsResponse"
                }
              }
            }
          },
          "400": {
            "description": "Bad Request",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/response.ErrorResponse"
                }
              }
            }
          },
          "500": {
            "description": "Internal Server Error",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/response.ErrorResponse"
                }
              }
            }
          }
        }
      }
    }
  },
  "components": {
    "schemas": {
      "response.ErrorCategory": {
        "type": "object",
        "properties": {
          "category": {
            "type": "string"
          },
          "grpc_status_code": {
            "type": "integer"
          },
          "http_status_code": {
            "type": "integer"
          }
        }
      },
      "response.ErrorDetails": {
        "type": "object",
        "properties": {
          "details": {
            "type": "string"
          },
          "key": {
            "type": "string"
          }
        }
      },
      "response.ErrorReason": {
        "type": "object",
        "properties": {
          "reason": {
            "type": "string"
          }
        }
      },
      "response.ErrorResponse": {
        "type": "object",
        "properties": {
          "error_category": {
            "$ref": "#/components/schemas/response.ErrorCategory"
          },
          "error_description": {
            "type": "string"
          },
          "error_details": {
            "type": "array",
            "items": {
              "$ref": "#/components/schemas/response.ErrorDetails"
            }
          },
          "error_reason": {
            "$ref": "#/components/schemas/response.ErrorReason"
          }
        }
      },
      "response.RequestedErcWithdrawalResponse": {
        "required": [
          "account_address",
          "amount",
          "call_data",
          "hash",
          "to_address",
          "token_address",
          "valid_after",
          "valid_before"
        ],
        "type": "object",
        "properties": {
          "account_address": {
            "type": "string",
            "description": "AccountAddress represents the account address associated with the withdrawal request",
            "example": 9.584885843247168e+47
          },
          "amount": {
            "type": "number",
            "description": "Amount specifies the value to be withdrawn, expressed as a floating-point number",
            "example": 100
          },
          "call_data": {
            "type": "string",
            "description": "CallData represents the encoded data required for executing the contract call",
            "example": "3F7D9E1C5A2B804D6E93F7C1A0B5D8E29F4A3B7C6D5E0F1A2B3C4D5E6F7A8B9"
          },
          "hash": {
            "type": "string",
            "description": "Hash represents calldata and nonce hash used to request this withdrawal",
            "example": 3.9148276998487085e+75
          },
          "to_address": {
            "type": "string",
            "description": "ToAddress specifies the destination address for the withdrawal",
            "example": 1.3976909197991362e+48
          },
          "token_address": {
            "type": "string",
            "description": "TokenAddress represents the blockchain address of the token involved in the withdrawal request",
            "example": 6.4956264143494794e+47
          },
          "valid_after": {
            "type": "string",
            "description": "ValidAfter specifies the timestamp after which the withdrawal request is considered valid",
            "example": "2021-01-01T00:00:00Z"
          },
          "valid_before": {
            "type": "string",
            "description": "ValidUntil indicates the expiry time of the withdrawal request",
            "example": "2021-01-01T00:00:00Z"
          }
        }
      },
      "response.RequestedErcWithdrawalsResponse": {
        "required": [
          "data"
        ],
        "type": "object",
        "properties": {
          "data": {
            "type": "array",
            "description": "Data contains a list of RequestedErcWithdrawalResponse objects",
            "items": {
              "$ref": "#/components/schemas/response.RequestedErcWithdrawalResponse"
            }
          }
        }
      }
    },
    "securitySchemes": {
      "Auth0Token": {
        "type": "apiKey",
        "description": "Token obtained using Auth0 client credentials grant flow. Please see [Authorization](#tag/Authorization/Auth0) section",
        "name": "Authorization",
        "in": "header"
      },
      "WirexPayToken": {
        "type": "apiKey",
        "description": "Wirex issued JWT token that can be obtained by using [Login as user](#tag/User/paths/~1user~1authorize/post) endpoint",
        "name": "Authorization",
        "in": "header"
      }
    }
  },
  "security": [
    {
      "WirexPayToken": []
    },
    {
      "Auth0Token": []
    }
  ],
  "x-readme": {}
}
```