@mauren.pagsuyuin

I just ran a quick test on API Playground. When I set {"inputVolatilityType": "Settle"} in the surfaceParameters, the response returned an error saying "Invalid input: Unbindable json. Error converting value \"Settle\" to type 'System.Nullable`1[TR.Qps.Models.MarketData.Enums.EVolatilityType]".

As the documentation says and as my test confirms, "Settle" enumerated value has been deprecated for inputVolatilityType parameter and it is no longer possible to use it.

Hi team, I wish to follow up

@Alex Putkov. THANK YOU! Internal has additional query:

1. Is there a timeline for the retirement of the usage of ‘Settle’ in the field of ‘inputVolatilityType’?
2. It was advised that the alternative for ‘inputVolatilityType’ is the 'timestamp'. Is there any documentation or manual for the alternative field ‘timestamp’? Or what is the difference for different values?

@mauren.pagsuyuin

1. As per my previous response, 'Settle' value is already removed from enumeration for inputVolatilityType parameter. It is no longer possible to use this value. In other words there cannot be a timeline for the retirement of this value because it is already retired.
2. If you'd like to use settlement values to build volatility surface, you should indeed use pricing parameter named timeStamp and set its value to 'Settle'. This parameter is described in the API documentation you referenced in your original post on this thread.