regis

RegentLoginPersonMatchRequest

**Requires Authentication**
Required role:	REGISUserRole

The following routes are available for this service:
POST	/RegentLogin/PersonMatch

import java.math.*
import java.util.*
import net.servicestack.client.*


open class RegentLoginPersonMatchRequest
{
    var first_name:String? = null
    var last_name:String? = null
    var email:String? = null
    var dob:Date? = null
    var regent_id:Int? = null
}

open class RegentLoginPersonMatchResponse
{
    var responseStatus:ResponseStatus? = null
    var regent_id:Int? = null
    var birthdate_exists:Boolean? = null
    var birthdate_matches:Boolean? = null
    var has_regent_login:Boolean? = null
    var is_a_regis_person:Boolean? = null
    var email_matches:Boolean? = null
}

Kotlin RegentLoginPersonMatchRequest 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 /RegentLogin/PersonMatch HTTP/1.1 
Host: data.regent-college.edu 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	first_name: String,
	last_name: String,
	email: String,
	dob: 0001-01-01,
	regent_id: 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,
	birthdate_exists: False,
	birthdate_matches: False,
	has_regent_login: False,
	is_a_regis_person: False,
	email_matches: False
}