| POST | /User/Travel |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserTravelProfileID | form | int | No | |
| DateArrived | form | DateTime | No | |
| DateDeparture | form | DateTime | No | |
| IsHidden | form | bool | No | |
| ShowSimpleDates | form | bool | No | |
| Description | form | string | No | |
| LocationGID | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| TextApprovalStatus | form | TravelProfileApprovalStatus | No | |
| LocationLabel | form | string | No | |
| LocationText | form | 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 /User/Travel HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/json
Content-Type: application/json
Content-Length: length
{"UserTravelProfileID":0,"DateArrived":"\/Date(-62135596800000-0000)\/","DateDeparture":"\/Date(-62135596800000-0000)\/","IsHidden":false,"ShowSimpleDates":false,"Description":"String","LocationGID":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"TextApprovalStatus":"Approved","LocationLabel":"String","LocationText":"String","UserTravelProfileID":0,"DateArrived":"\/Date(-62135596800000-0000)\/","DateDeparture":"\/Date(-62135596800000-0000)\/","IsHidden":false,"ShowSimpleDates":false,"Description":"String","LocationGID":"String"}