MediBuddy Mobile Services V1.1

GenericNotificationRequest

The following routes are available for this service:
POST	/user/sendFirebaseNotification/

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

<GenericNotificationRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <AdditionalProperties xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
    <d2p1:KeyValueOfstringstring>
      <d2p1:Key>String</d2p1:Key>
      <d2p1:Value>String</d2p1:Value>
    </d2p1:KeyValueOfstringstring>
  </AdditionalProperties>
  <NotificationData>
    <BodyMessage>String</BodyMessage>
    <Maid>0</Maid>
    <NotificationType>String</NotificationType>
    <TitleMessage>String</TitleMessage>
  </NotificationData>
  <SouceType xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
    <d2p1:string>String</d2p1:string>
  </SouceType>
</GenericNotificationRequest>

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

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