MediBuddy Mobile Services V1.1

SIUserVerifyOTPRequest

The following routes are available for this service:
POST	/claim/VerifySIOTP/

To override the Content-type in your clients 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 /xml/reply/SIUserVerifyOTPRequest HTTP/1.1 
Host: mb-mobile-api.medibuddy.in 
Content-Type: application/xml
Content-Length: length

<SIUserVerifyOTPRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <IPAddress xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</IPAddress>
  <MBToken xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</MBToken>
  <MobileDeviceModel xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</MobileDeviceModel>
  <PlatformVer xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</PlatformVer>
  <UserAgent xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</UserAgent>
  <UserPlatform xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</UserPlatform>
  <DeviceIdentity>String</DeviceIdentity>
  <EncryptedText>String</EncryptedText>
  <InitialVector>String</InitialVector>
  <OTP>String</OTP>
  <PasswordEncryption>String</PasswordEncryption>
</SIUserVerifyOTPRequest>

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

<SIUserVerifyOTPResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <ErrorMsg>String</ErrorMsg>
  <IsDeviceVerify>false</IsDeviceVerify>
</SIUserVerifyOTPResponse>