BackofficeApi

FeatureTypeListRequest

Backoffice

**Requires Authentication**
Required role:	Backoffice

The following routes are available for this service:
GET	/feature/types

**FeatureTypeListResponse** Parameters:
Name	Parameter	Data Type	Required	Description
FeatureGroups	form	List<FeatureGroupCategoryMatch>	Yes

**FeatureGroupCategoryMatch** Parameters:
Name	Parameter	Data Type	Required
CategorySlugPrefixes	form	List<string>	Yes
Group	form	FeatureGroup	No
FeatureTypes	form	List<FeatureTypeDto>	Yes

**FeatureGroup** Enum:
General
Fashion
FoodAndDrink

**FeatureTypeDto** Parameters:
Name	Parameter	Data Type	Required	Description
Slug	form	FeatureType	No
Label	form	string	Yes

**FeatureType** Enum:
BarSpeciality
BarType
Cuisine
SaveFoodAndMoney
MealType
Menu
OutdoorSeating
Parking
PaymentOptions
PriceMainDish
SubCategories
SubCategoriesAndBrands
EatingSuitabilities
TakeAway
WearPriceProfile
WheelChairAccessible
Wifi
WebShop
Filtering

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.

GET /feature/types HTTP/1.1 
Host: backoffice-api.brovs.com 
Accept: application/xml

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

<FeatureTypeListResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BackofficeApi.Dto">
  <FeatureGroups>
    <FeatureGroupCategoryMatch>
      <CategorySlugPrefixes xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
        <d4p1:string>String</d4p1:string>
      </CategorySlugPrefixes>
      <FeatureTypes>
        <FeatureTypeDto>
          <Label>String</Label>
          <Slug>BarSpeciality</Slug>
        </FeatureTypeDto>
      </FeatureTypes>
      <Group>General</Group>
    </FeatureGroupCategoryMatch>
  </FeatureGroups>
</FeatureTypeListResponse>