| POST | /SchedulerResponse | Get Reservations for asset reservation calendar |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserID | path | string | Yes | User Internal ID |
| SearchCriteriaCollection | path | List | No | Search Criteria Collection for Asset reservation calendar |
| IsReservationData | path | bool | No | Flag for weather coming from Reservation events or Asset resources |
| IsAssetReservationData | path | bool | No | Flag for weather coming from Asset reservation or reservation events |
| IsResourceData | path | bool | No | Flag for weather coming from Asset/Reservation events or resources |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| FieldID | body | string | No | |
| FieldName | body | string | No | |
| FieldValue | body | Object | No | |
| Operator | body | string | No | |
| FieldType | body | short | No | |
| UseMultiSelect | body | bool | No | |
| IsSearchAsTextbox | body | bool | No | |
| IsTransactionDetailSearch | body | bool | No | |
| IsSubTransactionDetailSearch | body | bool | No | |
| SecondDateRangeValue | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /json/reply/GetAssetReservationCalendar HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: application/json
Content-Length: length
{"UserID":"String","SearchCriteriaCollection":[{"FieldName":"String","FieldValue":{},"Operator":"String"}],"IsReservationData":false,"IsAssetReservationData":false,"IsResourceData":false}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length (string)