An operation is the transaction between two or more parties, where one of the parties is always the customer. The other party(ies) are called counterparties. The documentation provides information on the endpoints, responses, and possible errors for API requests for operations. It also includes minimalistic request examples.
POST
Path: {{baseUrl}}
/amlyze-ws-rest/validate-batch-operations
ContentType: application/json
Authorization: Basic Auth
/Bearer Token
POST
Path: {{baseUrl}}
/amlyze-ws-rest/batch-operations
ContentType: application/json
Authorization: Basic Auth
/Bearer Token
⚠️ Warning: Operations evaluation and screening not available in this service.
Error Description |
---|
CommunicationNumber is mandatory |
RiskManagementCategory is mandatory |
RiskManagementCategory does not exist in amlyze |
Requester is mandatory |
SourceOfRiskLevel is mandatory, allowed values: IMPORT / EVALUATE |
OperationExtId is mandatory |
OperationType is mandatory |
Problem with OperationType (INVALID). INVALID is not defined in Amlyze. Check Operation type classifier for available values |
Currency is mandatory, check Currency classifier codes for allowed values |
Currency is mandatory, check Currency classifier codes for allowed values |
SourceCountry is mandatory, check country classifier codes for allowed values |
DestinationCountry is mandatory, check country classifier codes for allowed values |
Description is mandatory |
Problem with OperationType (SEPA). Problem with OperationParties. No operation party account related to your institution BIC, or Customer |
Invalid FinancialFlowDirection. Your institution CREDITOR found for OUTGOING operation |
Problem with OperationType (SEPA). Problem with OperationParties. Invalid count of your institution operation parties for SEPA operationType |