TBS Apps API

<back to all web services

VerifyMFATokenRequest

Requires Authentication
The following routes are available for this service:
POST/VerifyMFATokenVerify mfa token for clientVerify mfa token for client
VerifyMFATokenRequest Parameters:
NameParameterData TypeRequiredDescription
MFATokenbodystringNoMFAToken
VerifyMFATokenResponse Parameters:
NameParameterData TypeRequiredDescription
VerificationAttemptsRemainingformintNo
ResponseDataBase Parameters:
NameParameterData TypeRequiredDescription
ErrorNoformintNo
MessageformstringNo
Identityformlong?No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /VerifyMFAToken HTTP/1.1 
Host: tstextweb20.np.bluebet.com.au 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<VerifyMFATokenRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <MFAToken>String</MFAToken>
</VerifyMFATokenRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<VerifyMFATokenResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <ErrorNo xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</ErrorNo>
  <Identity xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</Identity>
  <Message xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">String</Message>
  <VerificationAttemptsRemaining>0</VerificationAttemptsRemaining>
</VerifyMFATokenResponse>