A Participant can inquiry exception position values (Base, Lower, and Upper).
POST {{baseUrl}}/getExceptionPositionCalendar/:senderBic
The GetExceptionCalendar request allows the Participant to retrieve its own set of values (lower, base,upper and reset to base position) that will be applied for each LAC of a specific day in the future (or for the current business date). It is possible to inquire the calendar up to one year from the current day. If the Participant is an LP, it is allowed to send the GetExceptionPositionCalendar Request for those LSPs whose liquidity management is responsible for. Only the Owner of a Liquidity Pool can inquire the values of a Member belonging to its Pool. The returned values are the ones that will be really applied by the system, if an exception was set for the Business Date, it will be returned in place of the default values. The response contains the values for the request Business Day.
Request Body
{"dateTime"=>"2019-06-21T23:20:50.000001", "criteria"=>{"businessDate"=>"2019-06-21", "lspBic"=>"IPSDID21", "memberBic"=>"IPSDID21", "poolId"=>"IPSDID21XXX01"}}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
ivUserKey | string | The subscription key of a Participant. Following the format cn=<SSO+BIC+UserId+T>,o=BIC8,o=swift. SSO is a fixed string, last character is for environment (P for production and T for test) eg SSOUNCRITMMAPI12345P, o=uncritmm,o=swift | |
ivUserBic | string | ||
Content-Type | string | ||
Accept | string |
RESPONSES
status: OK
{"dateTime":"2019-06-21T23:20:50.000001","response":{"lspBic":"IPSDID21","bicExceptionDayValues":[{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"},{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"}],"memberBic":"IPSDID21","poolId":"IPSDID21XXX01","businessDate":"2019-06-21","memberExceptionDayValues":[{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"},{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"}]}}