PUT | /em/tour/vehicle/profile | update tour vehicle profile | Update Tour VehicleProfileID using Custom search fields |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
LocationID | query | Yes | Stop's locationId | |
VehicleProfileID | query | Yes | Vehicle Profile to update | |
SearchFieldContent | body | SearchFieldContent | Yes | Search Criteria on customData |
Token | query | Yes | The security token | |
Source | query | string | No | Name of the event provider: Examples are ptvemapp, ptvemportal, jmeter, any customer specific app |
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. The placeholders shown need to be replaced with actual values.
PUT /em/tour/vehicle/profile HTTP/1.1
Host: eta.cloud.ptvgroup.com
Content-Type: application/json
Content-Length: length
{
"locationID": "String",
"vehicleProfileID": "String",
"searchFieldContent": {
"searchFields": [
{
"fieldName": "String",
"fieldValue": "String",
"fieldLabel": "String"
}
]
},
"token": "String",
"source": "String"
}
The following are sample HTTP responses. The placeholders shown need to be replaced with actual values.
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } } }