| POST PUT | /amenityReservation |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| OperationalId | body | string | No | |
| AmenityKey | body | Guid | No | |
| AmenityId | body | int | No | |
| ReservationDate | body | DateTime | No | |
| StartTime | body | DateTime | No | |
| EndTime | body | DateTime | No | |
| Charge | body | decimal | No | |
| EventTitle | body | string | No | |
| Notes | body | string | No | |
| ReservationId | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| ResponseStatus | form | ResponseStatus | 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 /amenityReservation HTTP/1.1
Host: avalonaccessapi.avalonbay.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"operationalId":"String","amenityKey":"00000000-0000-0000-0000-000000000000","amenityId":0,"reservationDate":"0001-01-01 00:00:00","startTime":"0001-01-01 00:00:00","endTime":"0001-01-01 00:00:00","charge":0,"eventTitle":"String","notes":"String","reservationId":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"id":"String","responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}