MediBuddy Mobile Services V1.1

<back to all web services

IdentifyUserRequest

The following routes are available for this service:
POST/IdentifyUser

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

<IdentifyUserRequest 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>
  <ClaimId>0</ClaimId>
  <CompanyName>String</CompanyName>
  <DOB>String</DOB>
  <DOB1>0001-01-01T00:00:00</DOB1>
  <EmployeeId>String</EmployeeId>
  <IsMobNumRegOnWhatsApp>false</IsMobNumRegOnWhatsApp>
  <MobileNumber>0</MobileNumber>
  <Name>String</Name>
  <PolicyNumber>String</PolicyNumber>
</IdentifyUserRequest>