FirstChoice.API

AuctionFloorVehicle

**AuctionFloorVehicle** Parameters:
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

**GenericResponse** Parameters:
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 .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/AuctionFloorVehicle HTTP/1.1 
Host: staging-api.my1stchoicefs.net 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<AuctionFloorVehicle xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/FirstChoice.API.ServiceModel">
  <BOSAmount>0</BOSAmount>
  <BOSDate>0001-01-01T00:00:00</BOSDate>
  <Color>String</Color>
  <DealerId>00000000-0000-0000-0000-000000000000</DealerId>
  <Make>String</Make>
  <Miles>0</Miles>
  <Model>String</Model>
  <TitleNumber>String</TitleNumber>
  <TitleState>String</TitleState>
  <Vin>String</Vin>
  <Year>0</Year>
</AuctionFloorVehicle>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<GenericResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/FirstChoice.API.ServiceModel">
  <Message>String</Message>
  <Success>false</Success>
</GenericResponse>