You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -120,6 +120,7 @@ Field Key | Example Value | Field Format
120
120
"123",
121
121
"321"
122
122
],
123
+
startingPrice:34000,
123
124
stockNumber:"00100060",
124
125
transmission:"Variable",
125
126
trim:"Touring 2WD",
@@ -129,10 +130,33 @@ Field Key | Example Value | Field Format
129
130
}
130
131
```
131
132
132
-
Field Key | Example Value | Field Format
133
-
-------------- | -------------- | --------------
133
+
Vehicle pricing is a particularly flexible piece of our system. With flexibility often comes complexity, so we provide several fields on the vehicle object to simplify and standardize the pricing information for the API consumer.
134
+
135
+
`startingPrice` is the first pricing value displayed on the vehicle. It is often the highest price displayed to the user. In some cases a dealer fee can increase the price later in the pricing stack.
136
+
137
+
`finalPrice` is the lowest price displayed on the vehicle not including conditional incentives. This is intended to be the price that the dealership is willing to sell the vehicle at, less any special offers that are only applicable to some customers.
138
+
139
+
`highestPrice` is the greater of all of the available pricing field values. It is typically the highest price shown to the user on the page, but in some cases can be higher than what is displayed to the user. This field is `deprecated` and may be removed at a later date with sufficient notice.
140
+
141
+
It is recommended that you use `startingPrice` for the most expensive price displayed to the user and `finalPrice` for the least expensive price displayed to the user.
142
+
143
+
You may notice one or more of these fields available in the vehicle object on some sites:
144
+
145
+
`askingPrice`
146
+
`internetPrice`
147
+
`msrp`
148
+
`retailValue`
149
+
`salePrice`
150
+
`wholesalePrice`
151
+
152
+
All of the above fields are `deprecated`, meaning they may be removed from the API at a later date. New integrations should not use any of the above fields and should instead rely on `startingPrice` or `finalPrice` for the correct vehicle pricing information.
0 commit comments