...
| Expand | ||
|---|---|---|
| ||
curl --location 'https://staging-api.autoreturn.net/api-web/api/impound/lookup' \ |
Note that the limit is very important here, as you could end up returning many vehicles if you allow the user to select something very broad, like all toyotas towed in January.
...
VehicleId is the unique id for each time a vehicle gets towed. If it gets towed twice, it will get 2 vehicleIds. You then make a request to the /impound endpoint which will get you the complete vehicle details including the fees as of the time of the request.
| Expand | ||
|---|---|---|
| ||
curl --location 'https://staging-api.autoreturn.net/api-web/api/impound?id=1067632 |
for example will give a response containing most of the details of the vehicle. In particular you’ll want to look at
...
You then call the /createReceipt endpoint with the vehicleId and contact details the list of fees you want to pay. If you want to just always pay all of the fees then you can leave that element null or empty.
| Expand | ||
|---|---|---|
| ||
curl --location 'https://staging-api.autoreturn.net/api-web/api/impound/createReceipt' \ |
From this request you will receive a receiptIdreceipt Id (labeled just id in the response). This receipt must then be paid. call the /applyPayment endpoint with that receiptId and the details of the payment.
Note that even if a vehicle has been paid for, it might not be releasable if for example it has holds that prevent release.
| Expand | ||
|---|---|---|
| ||
curl --location 'https://staging-api.autoreturn.net/api-web/api/impound/applyPayment' \ |
Note the contactId was returned in the previous result. This allows you to reuse the same contact for who the receipt is issued to, and who is paying. Generally only the person the receipt is issued to can retrieve the vehicle from the lot, however this may vary by municipal policy.
Note that once a receipt has been created for a vehicle it must be paid for or voided.