POST | /v1/{VehicleType}/Vehicle/Exclusion |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
VehicleIdentifier | body | string | Yes | |
VehicleType | path | string | Yes |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Exclusions | form | List<VehicleExclusion> | Yes |
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 /v1/{VehicleType}/Vehicle/Exclusion HTTP/1.1
Host: uat-api-vehicle-mgt-mb-dhc.rapp-customers.co.uk
Accept: application/json
Content-Type: application/json
Content-Length: length
{"vehicleIdentifier":"String","vehicleType":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"exclusions":[{"vehicleIdentifier":"String","used":false,"userId":"String","exclusionDate":"\/Date(-62135596800000-0000)\/"}]}