regis

RegentLoginPersonMatchRequest

**Requires Authentication**
Required role:	REGISUserRole

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

**RegentLoginPersonMatchRequest** Parameters:
Name	Parameter	Data Type	Required
first_name	body	string	No
last_name	body	string	No
email	body	string	No
dob	body	DateTime?	No
regent_id	body	int?	No

**RegentLoginPersonMatchResponse** Parameters:
Name	Parameter	Data Type	Required
ResponseStatus	form	ResponseStatus	No
regent_id	form	int?	No
birthdate_exists	form	bool	No
birthdate_matches	form	bool	No
has_regent_login	form	bool	No
is_a_regis_person	form	bool	No
email_matches	form	bool	No

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
}