| Required role: | Admin |
| PATCH | /career_events/{CareerEventId} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| CareerEventId | path | int | No | |
| Name | query | string | No | |
| EventDt | query | DateTime? | No | |
| OpenDt | query | DateTime? | No | |
| CloseDt | query | DateTime? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | CareerEventDTO | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| CareerEventId | form | int | No | |
| Name | form | string | No | |
| EventDt | form | DateTime? | No | |
| OpenDt | form | DateTime? | No | |
| CloseDt | form | DateTime? | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PATCH //career_events/{CareerEventId} HTTP/1.1
Host: api.lsu-staging.abodehms.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
careerEventId: 0,
name: String,
eventDt: 0001-01-01,
openDt: 0001-01-01,
closeDt: 0001-01-01
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
result:
{
careerEventId: 0,
name: String,
eventDt: 0001-01-01,
openDt: 0001-01-01,
closeDt: 0001-01-01
},
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}