Accessibility, Parking & Payment
Filter venues by step-free access, accessible toilets, parking types and accepted payment methods.
These three preferences are filters. A venue must offer at least one of the values in each list you send.
"preferences": {
"accessibilityOptions": ["ENTRANCE", "BATHROOM"],
"parkingOptions": ["LOT", "GARAGE"],
"paymentOptions": ["NFC"]
}This example returns venues that have (an accessible entrance or an accessible toilet) and (a car park or a garage) and accept contactless payment.
Values are uppercase. Values not in these lists are ignored.
accessibilityOptions
| Value | Venue has… |
|---|---|
| ENTRANCE | a wheelchair-accessible entrance |
| BATHROOM | a wheelchair-accessible toilet |
| SEATING | wheelchair-accessible seating |
| PARKING | wheelchair-accessible parking |
parkingOptions
| Value | Venue has… |
|---|---|
| STREET | street parking nearby |
| LOT | a car park |
| GARAGE | a parking garage |
| VALET | valet parking |
paymentOptions
| Value | Venue accepts… |
|---|---|
| CREDIT | credit cards |
| DEBIT | debit cards |
| CASH | cash |
| NFC | contactless and mobile payments |
| ONLINE | online payment |
| AMEX | American Express |
| AMEX_FEE | American Express, with a surcharge |
| EXCL_AMEX | cards except American Express |
Need every option?
Because each list means "at least one of", you can't ask for a venue with both an accessible entrance and an accessible toilet in one request. Filter on the most important option, then check the accessibilityOptions, parkingOptions and paymentOptions returned by the Basic Details endpoint.
Missing data
Venues without data for an option are left out when you filter on it. If a filter returns very few results, consider ranking or labelling venues in your own UI instead.