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
{
public partial class AddFile
{
public virtual string Link { get; set; }
public virtual Guid? BlobID { get; set; }
public virtual int? Size { get; set; }
public virtual bool IsAttachment { get; set; }
public virtual bool Data { get; set; }
public virtual bool OCR { get; set; }
public virtual bool Preview { get; set; }
public virtual string Type { get; set; }
public virtual DateTime? DateTimeLastModified { get; set; }
public virtual int? MetricHeight { get; set; }
public virtual int? MetricWidth { get; set; }
public virtual Guid? DocumentID { get; set; }
public virtual string OriginalFileName { get; set; }
}
public partial class AddFileResponse
{
public virtual Guid FileID { get; set; }
}
}
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /jsv/reply/AddFile HTTP/1.1
Host: digiofficeapigateway.deltares.nl
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
Link: String,
BlobID: 00000000-0000-0000-0000-000000000000,
Size: 0,
IsAttachment: False,
Data: False,
OCR: False,
Preview: False,
Type: String,
DateTimeLastModified: 0001-01-01,
MetricHeight: 0,
MetricWidth: 0,
DocumentID: 00000000-0000-0000-0000-000000000000,
OriginalFileName: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
}