| POST | /smsStatus |
|---|
using System;
using System.IO;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using CPU.Notifications.ServiceModel;
namespace CPU.Notifications.ServiceModel
{
public partial class TwilioSMSEvent
{
public virtual string? AccountSid { get; set; }
public virtual string? APIVersion { get; set; }
public virtual int? ErrorCode { get; set; }
public virtual string? From { get; set; }
public virtual string? MessageSid { get; set; }
public virtual string? MessageStatus { get; set; }
public virtual string? MessagingServiceSid { get; set; }
public virtual string? SmsSid { get; set; }
public virtual string? SmsStatus { get; set; }
public virtual string? To { get; set; }
}
}
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /smsStatus HTTP/1.1
Host: cpmwebservices-t.clarkpud.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<TwilioSMSEvent xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/CPU.Notifications.ServiceModel">
<APIVersion>String</APIVersion>
<AccountSid>String</AccountSid>
<ErrorCode>0</ErrorCode>
<From>String</From>
<MessageSid>String</MessageSid>
<MessageStatus>String</MessageStatus>
<MessagingServiceSid>String</MessagingServiceSid>
<SmsSid>String</SmsSid>
<SmsStatus>String</SmsStatus>
<To>String</To>
</TwilioSMSEvent>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length (string)