Overview
The Withdraw API allows third-party partners to initiate cryptocurrency withdrawals on behalf of users and retrieve withdrawal history. All endpoints require API token authentication and are scoped to specific users.All endpoints require authentication via the
Authorization: Bearer <token> header. Generate your API key at Settings → API Key.Authentication
All requests must include an API token in the Authorization header:Create Withdrawal
Initiates a cryptocurrency withdrawal request for a user. The withdrawal is created as a queued transaction and processed asynchronously.Path Parameters
Request Body
Recipient Identifier (to parameter)
The to parameter accepts three formats:
-
Email address: Must contain
@symbol- Example:
[email protected]
- Example:
-
User ID: Must be a valid UUID
- Example:
550e8400-e29b-41d4-a716-446655440000
- Example:
-
Wallet address: Must start with
0xand be exactly 42 characters- Example:
0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb2
- Example:
When an email or user ID is provided, the system will automatically resolve it
to the user’s verified smart wallet address. If a wallet address is provided
directly, it will be used as-is.
Example Request
Response
string
Status message indicating the withdrawal was created
object
Example Response
Error Responses
string
Error message describing what went wrong
List Withdrawals
Retrieves a paginated list of withdrawal transactions for a user. Supports filtering by various criteria.Path Parameters
Query Parameters
Example Request
Response
string
Status message
object
array
Array of withdrawal objects. Each withdrawal includes:
string
Entry ID
string
Bulk payment ID
string
Current status of the withdrawal entry
string
Amount to be paid (as string for precision)
string
Currency code (e.g., USDT)
string
Recipient wallet address
string
External identifier, if provided
string
Blockchain transaction hash (if transaction has been processed)
string
Status of the token transfer on the blockchain
string
Error message, if the withdrawal failed
string
ISO 8601 timestamp of when the withdrawal was created
string
ISO 8601 timestamp of when the withdrawal was last updated
Example Response
Error Responses
Withdrawal Statuses
Withdrawals progress through the following statuses:Withdrawals are processed asynchronously. After creating a withdrawal, use the
bulkId returned in the response to query the withdrawal status via the List
Withdrawals endpoint.Rate Limits
Best Practices
-
Store the
bulkId: Always store thebulkIdreturned from the Create Withdrawal endpoint for tracking and reconciliation purposes. -
Use
externalId: Provide a uniqueexternalIdwhen creating withdrawals to easily track them in your system. -
Poll for status: After creating a withdrawal, periodically query the List Withdrawals endpoint using the
bulkIdorexternalIdto check the status. - Handle errors gracefully: Implement retry logic for transient errors, and handle blocked receivers appropriately.
- Validate amounts: Ensure amounts are provided as strings to maintain precision for decimal values.
-
Monitor transaction hashes: Once a withdrawal has a
transactionHash, you can track it on the blockchain explorer for the respective network.
Support
For API support, please contact:- Email: [email protected]
- Dashboard: LootRush Dashboard