regis

LetterSentRequest

**Requires Authentication**
Required role:	REGISUserRole

The following routes are available for this service:
POST	/correspondence

using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using regis.ClassLibrary.Requests;
using regis.ClassLibrary.Responses;

namespace regis.ClassLibrary.Requests
{
    public partial class LetterSentRequest
    {
        public virtual int pid { get; set; }
    }

}

namespace regis.ClassLibrary.Responses
{
    public partial class LetterSentResponse
    {
        public virtual ResponseStatus ResponseStatus { get; set; }
        public virtual int regent_id { get; set; }
        public virtual string document_name { get; set; }
        public virtual string document_description { get; set; }
        public virtual string program { get; set; }
        public virtual string letter_status { get; set; }
        public virtual string application_status { get; set; }
        public virtual DateTime? application_date { get; set; }
        public virtual DateTime? added_date { get; set; }
    }

}

C# LetterSentRequest DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /correspondence HTTP/1.1 
Host: data.regent-college.edu 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	pid: 0
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	responseStatus: 
	{
		errorCode: String,
		message: String,
		stackTrace: String,
		errors: 
		[
			{
				errorCode: String,
				fieldName: String,
				message: String,
				meta: 
				{
					String: String
				}
			}
		],
		meta: 
		{
			String: String
		}
	},
	regent_id: 0,
	document_name: String,
	document_description: String,
	program: String,
	letter_status: String,
	application_status: String,
	application_date: 0001-01-01,
	added_date: 0001-01-01
}