| Required role: | REGISUserRole |
| POST | /Terms/{term}/Update |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| authorizing_uuid | body | string | No | |
| term | path | string | No | |
| reporting_term | body | string | No | |
| reporting_year | body | int | No | |
| description | body | string | No | |
| start_date | body | DateTime? | No | |
| end_date | body | DateTime? | No | |
| registration_start_date | body | DateTime? | No | |
| registration_end_date | body | DateTime? | No | |
| drop_start_date | body | DateTime? | No | |
| drop_end_date | body | DateTime? | No | |
| add_start_date | body | DateTime? | No | |
| add_end_date | body | DateTime? | No | |
| grading_end_date | body | DateTime? | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /Terms/{term}/Update HTTP/1.1
Host: data.regent-college.edu
Accept: application/json
Content-Type: application/json
Content-Length: length
{"authorizing_uuid":"String","term":"String","reporting_term":"String","reporting_year":0,"description":"String","start_date":"0001-01-01T00:00:00.0000000","end_date":"0001-01-01T00:00:00.0000000","registration_start_date":"0001-01-01T00:00:00.0000000","registration_end_date":"0001-01-01T00:00:00.0000000","drop_start_date":"0001-01-01T00:00:00.0000000","drop_end_date":"0001-01-01T00:00:00.0000000","add_start_date":"0001-01-01T00:00:00.0000000","add_end_date":"0001-01-01T00:00:00.0000000","grading_end_date":"0001-01-01T00:00:00.0000000"}
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"}}