using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using IDB.API.DTO.Document.Operations;
namespace IDB.API.DTO.Document.Operations
{
    [DataContract]
    public partial class AddBlobFile
    {
        public AddBlobFile()
        {
            Image = new byte[]{};
        }
        [DataMember]
        public virtual string FileName { get; set; }
        [DataMember]
        public virtual string Type { get; set; }
        [DataMember]
        public virtual byte[] Image { get; set; }
        [DataMember]
        public virtual string ExternalID { get; set; }
    }
    public partial class AddBlobFileResponse
    {
        public virtual Guid BlobFileID { 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 /xml/reply/AddBlobFile HTTP/1.1 
Host: doapigw.baasbv.nl 
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<AddBlobFile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/IDB.API.DTO.Document.Operations">
  <ExternalID>String</ExternalID>
  <FileName>String</FileName>
  <Image>AA==</Image>
  <Type>String</Type>
</AddBlobFile>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <AddBlobFileResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/IDB.API.DTO.Document.Operations"> <BlobFileID>00000000-0000-0000-0000-000000000000</BlobFileID> </AddBlobFileResponse>