PharmacyServices

<back to all web services

Profiles

The following routes are available for this service:
GET/profile
POST/profile
Profiles Parameters:
NameParameterData TypeRequiredDescription
NamebodystringNo
EmailbodystringNo
PhonebodystringNo
CitybodystringNo
AddressbodystringNo
Profile Parameters:
NameParameterData TypeRequiredDescription
ContactformContactNo
PreferedPharmacyIdformlong?No
OrderCountformlongNo
ReservedBonusPointsformdoubleNo
BonusPointsformdoubleNo
HelloIdformlong?No
ContactIdformlong?No
PharmacyBaseEntity Parameters:
NameParameterData TypeRequiredDescription
IdformlongNo
Contact Parameters:
NameParameterData TypeRequiredDescription
NameformstringNo
EmailformstringNo
PhoneformstringNo
CityformstringNo
AddressformstringNo

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 /profile HTTP/1.1 
Host: mosapteka.inmar-tech.com 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<Profiles xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SBC.Pharm.Services.MobileAppService.Model">
  <Address>String</Address>
  <City>String</City>
  <Email>String</Email>
  <Name>String</Name>
  <Phone>String</Phone>
</Profiles>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<Profile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SBC.Pharm.Services.MobileAppService.Model">
  <Id>0</Id>
  <BonusPoints>0</BonusPoints>
  <Contact>
    <Id>0</Id>
    <Address>String</Address>
    <City>String</City>
    <Email>String</Email>
    <Name>String</Name>
    <Phone>String</Phone>
  </Contact>
  <ContactId>0</ContactId>
  <HelloId>0</HelloId>
  <OrderCount>0</OrderCount>
  <PreferedPharmacyId>0</PreferedPharmacyId>
  <ReservedBonusPoints>0</ReservedBonusPoints>
</Profile>