| POST | /ClientWithdrawalV2 |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| WithdrawalMethodID | body | int | No | Withdrwal Method Identifier - refer lookup data for types. Ex: Bank Transfer |
| BankName | body | string | No | Bank Name |
| BSBNumber | body | string | No | BSB Number |
| AccountNumber | body | string | No | Account Number |
| AccountName | body | string | No | Account Name |
| BPayBillerCode | body | string | No | BPay Biller Code |
| BPayRefNumber | body | string | No | BPay Reference Number |
| VipAccountToken | body | string | No | VipPreferred Account Token |
| Amount | body | decimal | No | Amount |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ErrorNo | form | int | No | |
| Message | form | string | No | |
| Identity | form | long? | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /ClientWithdrawalV2 HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"WithdrawalMethodID":0,"BankName":"String","BSBNumber":"String","AccountNumber":"String","AccountName":"String","BPayBillerCode":"String","BPayRefNumber":"String","VipAccountToken":"String","Amount":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ErrorNo":0,"Message":"String","Identity":0}