It allows the Participant to insert a new Reachable BIC linked to its same BIC.
PUT {{baseUrl}}/insertReachableBIC/:senderBIC
The insertReachableBIC request allows the participant to insert a new RB in SCT Routing Table. This function is managed under BCWS dual control and it generates an “Insert RB” operation logged as “TO BE AUTHORIZED”.
Request Body
{"dateTime"=>"2019-06-21T23:20:50.000001", "RBBICCode"=>"IPSDID21XXX", "initParticipantValidity"=>"2019-06-21", "endParticipantValidity"=>"2019-06-21", "parameters"=>{"name"=>"Merrill Lynch", "acceptanceDateAO1"=>true, "remittanceInformationERI"=>true, "ITATransferabilityAO3"=>true, "CAIUserGroup"=>true, "settlementCycles"=>"01; 02; 03; 04;", "sameBankingGroupAsDP"=>true}}
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":{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"},"operationRef":{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"}}