MediBuddy Mobile Services V1.1

VerifyNewUserOTPRequest

The following routes are available for this service:
POST	/verify/newuser/otp/

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/VerifyNewUserOTPRequest HTTP/1.1 
Host: mb-mobile-api.medibuddy.in 
Content-Type: application/xml
Content-Length: length

<VerifyNewUserOTPRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <DepToken>String</DepToken>
  <EmailEncCode>String</EmailEncCode>
  <EmailOTP>String</EmailOTP>
  <LoginName>String</LoginName>
  <MobEncCode>String</MobEncCode>
  <MobileOTP>String</MobileOTP>
  <Password>String</Password>
</VerifyNewUserOTPRequest>

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

<LoginResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <AuthServerToken>String</AuthServerToken>
  <AuthUserId>0</AuthUserId>
  <ErrorMessage>String</ErrorMessage>
  <IsEmailAvailable>false</IsEmailAvailable>
  <IsEmailVerified>false</IsEmailVerified>
  <IsMobileAvailable>false</IsMobileAvailable>
  <IsMobileVerified>false</IsMobileVerified>
  <LoginToken>String</LoginToken>
  <MaskedEmailId>String</MaskedEmailId>
  <RefreshToken>String</RefreshToken>
  <SSORedirectionUrl>String</SSORedirectionUrl>
  <Status>Default</Status>
  <UserAccessToken>String</UserAccessToken>
</LoginResponse>