EBA STEP2 SEPA Credit transfer
Number of APIs: 43
DPWS RESTful API for interacting with STEP2 SCT services Contact Support:
Email: api@ebaclearing.eu
1. It allows the Participant to inquire the Direct Participants list.
POST {{baseUrl}}/listParticipants/:senderBIC
The listParticipants request allows participants to retrieve the Direct Participants list. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
2. It allows the Participant to inquire the details of a Direct Participants.
POST {{baseUrl}}/participantDetails/:senderBIC
The participantDetails request allows participants to retrieve details of their Direct Participant. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
3. It allows the Participant to inquire the Reachable BICs list.
POST {{baseUrl}}/listReachableBICs/:senderBIC
The listReachableBICs request allows participants to retrieve the list of Reachable BICs in the routing table. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
4. It allows the Participant to inquire the details of a Reachable BIC.
POST {{baseUrl}}/RBDetails/:senderBIC
The RBDetails request allows a participant to retrieve details of its Reachable BIC in the routing table. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
5. It allows the Participant to inquire the list of its BPO relationships.
POST {{baseUrl}}/listBPORelationships/:senderBIC
The listBPORelationships request allows a participant to retrieve the list of its BPO relationships. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
6. It allows the Participant to insert a new BPO relationship.
PUT {{baseUrl}}/insertBPORelationship/:senderBIC
The insertBPORelationship request allows a participant to insert a new BPO Relationship for its BIC.
7. It allows the Participant to remove a BPO relationship.
PUT {{baseUrl}}/removeBPORelationship/:senderBIC
The removeBPORelationship request allows a participant to remove an existing BPO Relationship for its BIC.
8. It allows the Participant to remove its Reachable BICs.
PUT {{baseUrl}}/changeStatusReachableBIC/:senderBIC
The changeStatusReachableBIC request allows the participant to change the status of its RBs to DIS. This function is managed under BCWS dual control and it generates a “Remove RB” operation logged as “TO BE AUTHORIZED”.
9. 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”.
10. It allows the Participant to update its BIC.
PUT {{baseUrl}}/updateDirectParticipant/:senderBIC
The updateDirectParticipant request allows the participant to update its own DP in SCT Routing Table. This function is managed under BCWS dual control and it generates an “Update DP” operation logged as “TO BE AUTHORIZED”.
11. It allows the Participant to update a Reachable BIC linked to its same BIC.
PUT {{baseUrl}}/updateReachableBIC/:senderBIC
The updateReachableBIC request allows the participant to update its RBs in SCT Routing Table. This function is managed under BCWS dual control and it generates an "Update RB” operation logged as “TO BE AUTHORIZED”.
12. It allows the Participant to reject one of its provisioning operation previously inserted via API.
PUT {{baseUrl}}/rejectParticipantOperation/:senderBIC
The rejectParticipantOperation request allows the participant to reject a specific change operation submitted and not yet authorized.
13. It allows the Participant to enquire the list of its operations.
POST {{baseUrl}}/listOperations/:senderBIC
The listOperations request allows the participant to retrieve its routing table operations, based on a customized search criteria.
14. It allows the Participant to retrieve the details of a specific operation.
POST {{baseUrl}}/operationDetails/:senderBIC
The operationDetails request allows the participant to retrieve details of specific routing table operations for its BIC.
15. It allows the Participant to inquire the Default Thresholds list.
POST {{baseUrl}}/listDefaultThresholds/:senderBIC
The listDefaultThresholds request allows participants to retrieve the list of their Default Thresholds. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
16. It allows the Participant to update a specific Default Threshold.
PUT {{baseUrl}}/updateDefaultThreshold/:senderBIC
The updateDefaultThresholds request allows participants to update a specific Default Threshold.
17. It allows the Participant to inquire its debit position against specific Counterparty BIC not configured for settling in CGS.
POST {{baseUrl}}/debitPosition/:senderBIC
The debitPosition request allows participants to retrieve their debit position to be settled in T2I against the System or a specific Counterparty BIC configured for settling in T2I. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
18. It allows the Participant to inquire its debit position against a specific Counterpary BIC configured for settling in CGS.
POST {{baseUrl}}/debitPositionCGS/:senderBIC
The debitPositionCGS request allows participants to retrieve details on their debit position to be settled in CGS against the System or a specific Counterparty BIC configured for CGS. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
19. It allows to inquire the Transactions sent or received by the Participant.
POST {{baseUrl}}/listTransactions/:senderBIC
The listTransactions request allows a participant to retrieve the list of transactions for which its BIC is sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
20. It allows to get the details of a specific transaction sent or received by the Participant.
POST {{baseUrl}}/transactionDetails/:senderBIC
The transactionDetails request allows participants to get the details of a specific transaction for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
21. It allows to inquire the bulks contained in a file sent or received by the Participant.
POST {{baseUrl}}/listBulks/:senderBIC
The listBulks request allows participants to retrieve the list of bulks contained in files for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
22. It allows to get the details of a specific bulk contained in a file sent or received by the Participant.
POST {{baseUrl}}/bulkDetails/:senderBIC
The bulkDetails request allows participants to get the details of a specific bulk contained in files for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response
23. It allows to enquire the list of the files sent or received by the Participant.
POST {{baseUrl}}/listFiles/:senderBIC
The listFiles request allows participants to retrieve the list of files for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
24. It allows to get the details of a specific file sent or received by the Participant.
POST {{baseUrl}}/fileDetails/:senderBIC
The fileDetails request allows participants to get the details of a specific file for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
25. It allows to enquire the list of the messages sent or received by the Participant.
POST {{baseUrl}}/listMessages/:senderBIC
The listMessagesrequest allows participants to retrieve the list of messages for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
26. It allows to get the details of a specific message sent or received by the Participant.
POST {{baseUrl}}/messageDetails/:senderBIC
The messageDetails request allows participants to get the details of a specific message for which they are sender or receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
27. It allows to ask for the resending of a single file for which the Participant was the receiver.
POST {{baseUrl}}/retransmitOutFiles/:senderBIC
The retransmitOutFiles request allows participants to ask for the resending of a single file in ERR (error) – TSD (transmitted) – TSG (transmitting) status and for which the participant was the receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
28. It allows the Participant to ask the comprehensive re-transmission of output files for which the Participant was the receiver.
POST {{baseUrl}}/resendAll/:senderBIC
The resendAll allows a participant to ask the comprehensive re-transmission of all the output files in TSG (transmitting) or ERR (error) status and for which such participant was the receiver. If no record is found for the selected criteria of the request, the HTTP Code 204 is returned with the Response.
29. It allows to ask for the resending of a single message for which the Participant was the receiver.
POST {{baseUrl}}/retransmitOutMessages/:senderBIC
The retransmitOutMessages request allows participants to ask for the resending of a single message in ERR (error) – TSD (transmitted) – TSG (transmitting) status and for which the participant was the receiver. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
30. It allows the Participant to ask the cancellation of a bulk processed in Bulk Processing mode before the settlement takes place.
PUT {{baseUrl}}/bulkCancellation/:senderBIC
The bulkCancellation request allows participants to ask the cancellation of a bulk processed in Bulk Processing mode before the settlement of the included CT transactions takes place. Only bulks of pacs.008 (CT bulk messages) can be cancelled. The cancellation of a bulk is accepted only in case the included transactions are in suitable status (either“Positively Validated” or “Rejected” (from validation)). If there is at least one transaction of the bulk that is in a different status, the bulk cannot be cancelled. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
31. It allows the Participant to ask the cancellation of a bulk processed in Batch Processing mode before the settlement takes place.
PUT {{baseUrl}}/batchCancellation/:senderBIC
The batchCancellation allows participants to ask the cancellation of a bulk processed in Batch Processing mode before the settlement takes place. Only positively validated batches concerning pacs.008 (CT bulk messages) can be cancelled before settlement. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
32. It allows to ask for the creation of an offline report (valid only for the transactions processed in bulk processing mode).
POST {{baseUrl}}/reportRequest/:senderBIC
The reportRequest allows participants to ask for the creation of an offline report (valid only for the transactions processed in bulk processing mode). If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
33. It allows to enquire the list of the offline report generated after the “ReportRequest” API (valid only for the transactions processed in bulk processing mode).
POST {{baseUrl}}/listReport/:senderBIC
The listReport allows participants to retrieve the list of the offline report generated after the “ReportRequest” API (valid only for the transactions processed in bulk processing mode). If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
34. It allows to ask for the receiving of an offline report generated after the “ReportRequest” API (valid only for the transactions processed in bulk processing mode).
POST {{baseUrl}}/reportReceivingRequest/:senderBIC
The reportReceivingRequest allows participants to request the reception of an offline report generated after the “ReportRequest” API (valid only for the transactions processed in bulk processing mode). If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
35. It allows to ask for the creation of the Third Pole Reconciliation report.
POST {{baseUrl}}/thirdPoleReportRequest/:senderBIC
The thirdPoleReportRequest allows participants to request the creation of the Third Pole Reconciliation report. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
36. It allows to ask for the list of the Third Pole Reconciliation report generated after the “ThirdPoleReportRequest” API.
POST {{baseUrl}}/listThirdPoleReport/:senderBIC
The listThirdPoleReport allows participants to ask for the list of the Third Pole Reconciliation report generated after the “ThirdPoleReportRequest” API. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
37. It allows to ask for the receiving of the Third Pole Reconciliation report generated after the “ThirdPoleReportRequest” API.
POST {{baseUrl}}/thirdPoleReportReceivingRequest/:senderBIC
The thirdPoleReportReceivingRequest allows participants to request the reception of the Third Pole Reconciliation report generated after the “thirdPoleReportRequest” API. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
38. It allows to ask for the creation of the original xml of the message (valid only for the transactions processed in bulk processing mode).
POST {{baseUrl}}/originalXML/:senderBIC
The originalXML allows participants to retrieve of the original xml of the message (valid only for the transactions processed in bulk processing mode). If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
39. It allows the Participant to enquire the status of Commands that were submitted by the Participant.
POST {{baseUrl}}/listCommands/:senderBIC
The listCommands request allows participants to retrieve the list of their submitted commands. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
40. It allows the Participant to retrieve the details of a single command submitted by the Participant.
POST {{baseUrl}}/commandDetail/:senderBIC
The commandDetail request allows participants to retrieve the details of a single command submitted in DPWS. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
41. It allows the Participant to inquire the list of alerts produced by the System for its BIC.
POST {{baseUrl}}/listAlerts/:senderBIC
The listAlerts request allows participant to retrieve the list of alerts produced by the System for their BIC. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
42. It allows to enquire the list of LCRs generated for the Participant by SCT Service.
POST {{baseUrl}}/listLCR/:senderBIC
The listLCR request allows participants to retrieve the list of their LCRs. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
43. It allows the Participant to inquire details of a specific LCR.
POST {{baseUrl}}/lcrDetails/:senderBIC
The lcrDetails request allows participants to retrieve the details of a specific LCR. If no record is found for the set criteria of the request, the HTTP Code 204 is returned with the Response.
ENDPOINTS