| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BOSDate | query | DateTime | Yes | |
| DealerId | query | Guid | Yes | |
| Vin | query | string | Yes | Must be 17 characters |
| Year | query | int | Yes | |
| Make | query | string | Yes | |
| Model | query | string | Yes | |
| Miles | query | int | Yes | |
| Color | query | string | Yes | |
| BOSAmount | query | double | Yes | |
| TitleNumber | query | string | No | |
| TitleState | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Message | form | string | No | |
| Success | form | bool | 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 /json/reply/AuctionFloorVehicle HTTP/1.1
Host: staging-api.my1stchoicefs.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"BOSDate":"0001-01-01T00:00:00.0000000","Vin":"String","Year":0,"Make":"String","Model":"String","Miles":0,"Color":"String","BOSAmount":0,"TitleNumber":"String","TitleState":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Message":"String","Success":false}