TBS Apps API

ContentfulFeatureFlagRequest

The following routes are available for this service:
GET,POST	/Home/FeatureFlags	Gets feature flags	Gets feature flags from contentful

**ContentfulFeatureFlagResponse** Parameters:
Name	Parameter	Data Type	Required	Description
FeatureFlags	form	List<FeatureFlag>	No

**ResponseDataBase** Parameters:
Name	Parameter	Data Type	Required
ErrorNo	form	int	No
Message	form	string	No
Identity	form	long?	No

**FeatureFlag** Parameters:
Name	Parameter	Data Type	Required	Description
Name	form	string	No
IsEnabled	form	bool	No

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.

POST /Home/FeatureFlags HTTP/1.1 
Host: tstextweb20.np.bluebet.com.au 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<ContentfulFeatureFlagRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions" />

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

<ContentfulFeatureFlagResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <ErrorNo xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</ErrorNo>
  <Identity xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">0</Identity>
  <Message xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">String</Message>
  <FeatureFlags xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
    <d2p1:FeatureFlag>
      <d2p1:IsEnabled>false</d2p1:IsEnabled>
      <d2p1:Name>String</d2p1:Name>
    </d2p1:FeatureFlag>
  </FeatureFlags>
</ContentfulFeatureFlagResponse>