Skip to main content

Stock feeds

A dealer's stock can be sent to marketplaces and ad channels as well as their own website: AutoTrader, CarGurus, Motors, the Facebook & Instagram catalogue, Google vehicle ads and others, depending on what they have connected in the DMS. Each vehicle has a switch for each feed. With the API you can:

  • list the feeds a dealer can send stock to;
  • see, for one vehicle, whether each feed is live, waiting or held back, and why;
  • switch feeds on or off for one vehicle, or for up to 500 vehicles in one request.

These are the same switches as on the DMS vehicle page and the stock list, and they behave the same way. Reading needs the vehicles:read scope and changing needs vehicles:write. Both need a secret key or OAuth token, because a publishable key cannot see feeds.

Stock feeds are part of the dealer's plan. If their plan does not include them, the two read endpoints return an empty list and a change is refused with 403 stock_feeds_not_enabled. A test key gets the same answers, since a sandbox never sends stock anywhere.

The website is not a feed

Whether a vehicle shows on the dealer's own website is published_on_website on the vehicle itself. Change it with PATCH /v1/vehicles/{id}. That works on every plan.

List the dealer's feeds​

curl https://api.vehiso.com/v1/stock-feeds \
-H "Authorization: Bearer $VEHISO_SECRET_KEY"
{
"data": [
{ "code": "AUTOTRADER", "name": "AutoTrader", "switchable": true },
{ "code": "CARGURUS", "name": "CarGurus", "switchable": true },
{ "code": "META_CATALOGUE", "name": "Facebook & Instagram", "switchable": true }
]
}

The code is what you send to switch a feed. Only feeds the dealer has connected are listed, so the list differs between dealers. switchable is false for a feed that sends all of the dealer's stock and has no per-vehicle switch.

See where a vehicle is advertised​

curl https://api.vehiso.com/v1/vehicles/$VEHICLE_ID/feeds \
-H "Authorization: Bearer $VEHISO_SECRET_KEY"
{
"data": [
{
"code": "AUTOTRADER",
"name": "AutoTrader",
"on": true,
"state": "live",
"reasons": [],
"detail": null,
"sent_at": "2026-11-19T16:02:11Z"
},
{
"code": "CARGURUS",
"name": "CarGurus",
"on": true,
"state": "problem",
"reasons": ["NO_PHOTOS"],
"detail": null,
"sent_at": null
}
]
}
FieldMeaning
onWhether the vehicle's switch for this feed is on
statelive on the channel, pending waiting for the next send, problem held back, off not being sent
reasonsWhy it is not live, most important first, for example NO_PHOTOS, NO_PRICE, NOT_FOR_SALE, SWITCHED_OFF or AUTOTRADER_REJECTED
detailThe channel's own words where it gave a reason, such as AutoTrader's rejection reason. Not translated
sent_atWhen the vehicle was last sent

A switch that is on does not always mean the vehicle is live. A sold vehicle, or one with no photos or price, is held back until that is fixed, and reasons says what to fix.

Switch feeds for one vehicle​

Send the feeds you want to change, each set to true (on) or false (off). Feeds you do not name are left as they are.

curl -X PATCH https://api.vehiso.com/v1/vehicles/$VEHICLE_ID/feeds \
-H "Authorization: Bearer $VEHISO_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{"feeds": {"AUTOTRADER": true, "CARGURUS": false}}'

The answer is the vehicle's feeds after the change, in the same shape as GET /v1/vehicles/{id}/feeds. Switching AutoTrader on sends the advert to AutoTrader straight away, as it does in the DMS.

Switch feeds for many vehicles​

POST /v1/vehicles/feeds takes up to 500 vehicle ids and the same feeds object:

curl https://api.vehiso.com/v1/vehicles/feeds \
-H "Authorization: Bearer $VEHISO_SECRET_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: feeds-2026-11-20-cargurus-on" \
-d '{
"vehicle_ids": ["9b2f6c1e-4d7a-4e3b-8f0c-2a1d5e6b7c8d", "3c8e1f2a-6b5d-4a7c-9e0f-1d2b3c4a5e6f"],
"feeds": {"CARGURUS": true}
}'
{
"data": {
"updated": 2,
"vehicle_ids": ["9b2f6c1e-4d7a-4e3b-8f0c-2a1d5e6b7c8d", "3c8e1f2a-6b5d-4a7c-9e0f-1d2b3c4a5e6f"],
"feeds": {"CARGURUS": true}
}
}

A bulk change is all or nothing. If any id is not a vehicle your key can see (on a branch outside the key's branches, for example), or any feed is one the dealer cannot switch, the request is refused with 422 validation_failed and nothing changes. errors names the problem, such as vehicle_ids.1 or feeds.AUTOTRADER. Correct it and send the request again.

Errors​

Status and codeMeaning
403 stock_feeds_not_enabledThe dealer's plan does not include stock feeds
403 insufficient_scopeThe key lacks vehicles:read or vehicles:write
404 not_foundNo vehicle this key can see has that id
422 validation_failedA feed the dealer has not connected, an unknown vehicle in a bulk request, or a malformed body