Skip to main content

Listing Layout

How the shop's booking page lists its items, and for the price list layout, whether every hire length gets its own column. The portal, the website builder, the API and Dash all save these the same way.

Endpoints​

GET   /v1/settings/listing-layout    (read)
PATCH /v1/settings/listing-layout    (write)

Reading needs the settings:read scope. Writing needs settings:write.

Fields​

FieldTypeValuesDescription
layoutstringgrid, list, tile, editorial, showcase, bento, mosaic, pricelistHow items are laid out. pricelist lists every item by category with no photos
price_list_all_lengthsbooleanPrice list only. true (the default) shows a price for each hire length the shop has set; false shows one price per item, for the length the customer picked

A shop that lets customers pick any pickup and return time has no set hire lengths, so its price list shows one price per item whatever price_list_all_lengths says.

Read the settings​

curl https://app.equipdash.com/api/v1/settings/listing-layout \
  -H "Authorization: Bearer YOUR_API_KEY"
{
  "data": {
    "layout": "pricelist",
    "price_list_all_lengths": true
  },
  "meta": {
    "request_id": "req_abc123",
    "timestamp": "2026-10-07T12:00:00+00:00"
  }
}

Update the settings​

Send only the fields you want to change. The response is the full set, as GET returns it.

curl -X PATCH https://app.equipdash.com/api/v1/settings/listing-layout \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "layout": "pricelist",
    "price_list_all_lengths": false
  }'

Errors​

A layout outside the list returns 422 with the field named in error.details.

Collections​

A collection page sets its own layout with PATCH /v1/collections/{id}. Collections mix rentals, experiences and store items on one page, so they use the seven card layouts and refuse pricelist.