regis

PersonKeyRequest

**Requires Authentication**
Required role:	REGISUserRole

The following routes are available for this service:
POST	/person/keys

**PersonKeyRequest** Parameters:
Name	Parameter	Data Type	Required
regent_id	body	int	No
uuid	body	string	No
regent_login	body	string	No
regent_network_login	body	string	No

**PersonKeyResponse** Parameters:
Name	Parameter	Data Type	Required
ResponseStatus	form	ResponseStatus	No
regent_id	form	int	No
re_id	form	int	No
sugar_id	form	string	No
uuid	form	string	No
student_id	form	int?	No
regent_login	form	string	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 /person/keys HTTP/1.1 
Host: data.regent-college.edu 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	regent_id: 0,
	uuid: String,
	regent_login: String,
	regent_network_login: String
}

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,
	re_id: 0,
	sugar_id: String,
	uuid: String,
	student_id: 0,
	regent_login: String
}