[API]: Show triggered bounds on market data API

[JonRay15]

API Overview

In order to ... make price monitoring bounds clearer
We will build an API to... expose all bounds including triggered ones on the market data API
So that ... it is very clear the full set of bounds on a market, which have triggered, and which have not

API request details

• Show ALL price monitoring bounds even once they are triggered (currently once they are triggered they are not shown)
• Include some "status" on each bound which would be say "active" or "triggered"
• When a bound has been triggered we'd need to display "null" or "na" or similar for the referencePrice, minValidPrice, and maxValidPrice presumably

Filtering requirements (inputs)

• None

Sample API output (optional)

Current API output

"priceMonitoringBounds": [
{
"minValidPrice": "626861",
"maxValidPrice": "649827",
"trigger": {
"horizon": "360",
"probability": "0.9999999",
"auctionExtension": "300"
},
"referencePrice": "638244"
},
{
"minValidPrice": "618730",
"maxValidPrice": "664897",
"trigger": {
"horizon": "1440",
"probability": "0.9999999",
"auctionExtension": "1800"
},
"referencePrice": "641413"
},
{
"minValidPrice": "603653",
"maxValidPrice": "683785",
"trigger": {
"horizon": "4320",
"probability": "0.9999999",
"auctionExtension": "3600"
},
"referencePrice": "642514"
},
{
"minValidPrice": "558662",
"maxValidPrice": "738235",
"trigger": {
"horizon": "21600",
"probability": "0.9999999",
"auctionExtension": "86400"
},
"referencePrice": "642422"
}
],

Additional Details (optional)

Any additional information that provides context or gives information that will help us develop the feature.

[JonRay15]

Barney is considering options here