| Required role: | Admin |
| All Verbs | /wing |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| WingId | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | WingDTO | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| WingId | form | int | No | |
| WingName | form | string | No | |
| BuildingId | form | int | No | |
| Active | form | bool | 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 //wing HTTP/1.1
Host: api.lsu-staging.abodehms.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"wingId":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"result":{"wingId":0,"wingName":"String","buildingId":0,"active":false},"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}