regis

PersonAssignRegentLoginRequest

**Requires Authentication**
Required permission:	CreatePerson

The following routes are available for this service:
POST	/person/{regent_id}/assignRegentLogin

**PersonAssignRegentLoginRequest** Parameters:
Name	Parameter	Data Type	Required	Description
regent_id	path	int	No
regent_login	body	string	No

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

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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

POST /person/{regent_id}/assignRegentLogin HTTP/1.1 
Host: data.regent-college.edu 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"regent_id":0,"regent_login":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}