| PUT | /bootrecord/attempt/{id} | Updates boot record status. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | path | Guid | Yes | The Collection Attempt Id. |
| Status | query | int | Yes | The boot record status. |
| QueuedForTowReason | query | Guid | No | The queued for tow reason. |
| TowDispatchCompany | query | Guid | No | The tow dispatch company. |
| QueuedForReleaseReason | query | Guid | No | The queued for release reason. |
| IsBootMissing | query | bool | No | Whether the boot is missing to work with runaway status. |
| ChargeForMissingBoot | query | bool | No | Whether the we should add a lost fee for runaway status. |
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.
PUT /bootrecord/attempt/{id} HTTP/1.1
Host: api.paylock.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"id":"00000000-0000-0000-0000-000000000000","status":0,"queuedForTowReason":"00000000-0000-0000-0000-000000000000","towDispatchCompany":"00000000-0000-0000-0000-000000000000","queuedForReleaseReason":"00000000-0000-0000-0000-000000000000","isBootMissing":false,"chargeForMissingBoot":false}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length false