# AMLYZE > AMLYZE Documentation ## Docs - [Account import](https://api.amlyze.com/api-reference/account/account-import.md): This section provides information how to submit account details to our database. - [Batch import of account balances](https://api.amlyze.com/api-reference/account/batch-import-of-account-balances.md) - [Batch import of accounts](https://api.amlyze.com/api-reference/account/batch-import-of-accounts.md): Batch data import involve processing large volumes of account data at once. - [Update account balance](https://api.amlyze.com/api-reference/account/update-account-balance.md): This section provides detailed information on the endpoints that can be used to create and manage account balances. - [Validate batch of accounts without saving](https://api.amlyze.com/api-reference/account/validate-batch-of-accounts-without-saving.md): This method sends data only for validating JSON. - [Account Type](https://api.amlyze.com/api-reference/classifiers/account-type.md) - [Activity Type](https://api.amlyze.com/api-reference/classifiers/activity-type.md) - [Address Type](https://api.amlyze.com/api-reference/classifiers/address-type.md) - [Appeal Reason Type](https://api.amlyze.com/api-reference/classifiers/appeal-reason-type.md) - [Business Unit](https://api.amlyze.com/api-reference/classifiers/business-unit.md) - [Card Operation SubType](https://api.amlyze.com/api-reference/classifiers/card-operation-subtype.md) - [Country](https://api.amlyze.com/api-reference/classifiers/country.md) - [Currency](https://api.amlyze.com/api-reference/classifiers/currency.md) - [Decision Ground](https://api.amlyze.com/api-reference/classifiers/decision-ground.md) - [Income Source Type](https://api.amlyze.com/api-reference/classifiers/income-source-type.md) - [Introduction Source Type](https://api.amlyze.com/api-reference/classifiers/introduction-source-type.md) - [Legal Form](https://api.amlyze.com/api-reference/classifiers/legal-form.md) - [Operation Type](https://api.amlyze.com/api-reference/classifiers/operation-type.md) - [Payment Purpose Type](https://api.amlyze.com/api-reference/classifiers/payment-purpose-type.md) - [Relation Type](https://api.amlyze.com/api-reference/classifiers/relation-type.md) - [Risk Management Category](https://api.amlyze.com/api-reference/classifiers/risk-management-category.md) - [Service Type](https://api.amlyze.com/api-reference/classifiers/service-type.md) - [Source Of Wealth](https://api.amlyze.com/api-reference/classifiers/source-of-wealth.md) - [Turnover Type](https://api.amlyze.com/api-reference/classifiers/turnover-type.md) - [Communication Events by Communication Number](https://api.amlyze.com/api-reference/communication-events/communication-events-by-communication-number.md): Retrieves communication events by communication number. This can be used as fallback approach to get information about request. However keep in mind that not all request triggers webhook sending and not all webhooks that are sent have communication number. - [Contract registration](https://api.amlyze.com/api-reference/contract/contract-registration.md): This section provides detailed information on the endpoints that can be used to create and manage contracts. Contracts can be any type of documents with custom set of fields/elements. - [Update contract](https://api.amlyze.com/api-reference/contract/update-contract.md) - [Validate a batch of contracts without saving](https://api.amlyze.com/api-reference/contract/validate-a-batch-of-contracts-without-saving.md): This method sends data only for validating JSON. - [Validate and save a batch of contracts](https://api.amlyze.com/api-reference/contract/validate-and-save-a-batch-of-contracts.md): This method sends data and imports contracts in AMLYZE. - [Customer kyc scoring completed](https://api.amlyze.com/api-reference/customer-assessment/customer-kyc-scoring-completed.md): Fired when on completion by a human decision/automatically resolution. - [Customer kyc scoring pending](https://api.amlyze.com/api-reference/customer-assessment/customer-kyc-scoring-pending.md): Fired when a customer KYC score is pending and human decision is needed. - [Customer kyc scoring waiting for approval date](https://api.amlyze.com/api-reference/customer-assessment/customer-kyc-scoring-waiting-for-approval-date.md): Fired when configuration is set to wait for customer approval date. - [Customer retrospective completed](https://api.amlyze.com/api-reference/customer-assessment/customer-retrospective-completed.md): ❗ Fired ONLY on completion by a human decision. - [Customer retrospective pending](https://api.amlyze.com/api-reference/customer-assessment/customer-retrospective-pending.md): Fired when a customer retrospective risk management process is pending and human decision is needed. - [Customer assessment](https://api.amlyze.com/api-reference/customer-getters/customer-assessment.md): This endpoint retrieves customer assessment by its unique GUID. - [Customer retrospective assessment](https://api.amlyze.com/api-reference/customer-getters/customer-retrospective-assessment.md): This endpoint retrieves a retrospective assessment by its unique GUID. - [Customer screening](https://api.amlyze.com/api-reference/customer-getters/customer-screening.md): This endpoint retrieves a screening alert by its unique GUID. - [Customer adverse media screening completed](https://api.amlyze.com/api-reference/customer-screening/customer-adverse-media-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Customer adverse media screening pending](https://api.amlyze.com/api-reference/customer-screening/customer-adverse-media-screening-pending.md): Fired when a customer adverse media screening process is pending and human decision is needed. - [Customer internal list screening completed](https://api.amlyze.com/api-reference/customer-screening/customer-internal-list-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Customer internal list screening pending](https://api.amlyze.com/api-reference/customer-screening/customer-internal-list-screening-pending.md): Fired when a customer internal list screening process is pending and human decision is needed. - [Customer pep screening completed](https://api.amlyze.com/api-reference/customer-screening/customer-pep-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Customer pep screening pending](https://api.amlyze.com/api-reference/customer-screening/customer-pep-screening-pending.md): Fired when a customer PEP screening process is pending and human decision is needed. - [Customer sanctions screening completed](https://api.amlyze.com/api-reference/customer-screening/customer-sanctions-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Customer sanctions screening pending](https://api.amlyze.com/api-reference/customer-screening/customer-sanctions-screening-pending.md): Fired when a customer sanctions screening process is pending and human decision is needed. - [Batch Import of customers](https://api.amlyze.com/api-reference/customer/batch-import-of-customers.md): This method sends data and creates assessments in Amlyze. Note: Customer evaluation and screening are not available in this service. - [Customer updated](https://api.amlyze.com/api-reference/customer/customer-updated.md): Fired when a customer's data is updated. - [Evaluate customer](https://api.amlyze.com/api-reference/customer/evaluate-customer.md): To initiate the scoring process, the `sourceOfRiskLevel` field in the API payload must be set to `EVALUATE`. This instructs the AMLYZE engine to run the customer's data through the active risk matrix. In contrast, sending the value `IMPORT` will only update the customer's data in the system without… - [Validate batch of customers without saving](https://api.amlyze.com/api-reference/customer/validate-batch-of-customers-without-saving.md): This method sends data only for validating JSON and does not create any assessments in AMLYZE. - [Move operation to archive](https://api.amlyze.com/api-reference/integration-services/move-operation-to-archive.md): Move operation to archive. Operations in archive are not included in retro monitoring processes. - [Operation realtime completed](https://api.amlyze.com/api-reference/operation-assessment/operation-realtime-completed.md): Fired when on completion by a human decision/automatically resolution. - [Operation realtime pending](https://api.amlyze.com/api-reference/operation-assessment/operation-realtime-pending.md): Fired when a real-time operation risk management process is pending and human decision is needed. - [Operation assessment](https://api.amlyze.com/api-reference/operation-getters/operation-assessment.md): This endpoint retrieves an assessment by its unique GUID. - [Operation screening](https://api.amlyze.com/api-reference/operation-getters/operation-screening.md): This endpoint retrieves a screening alert by its unique GUID. - [Operation Reconciliation](https://api.amlyze.com/api-reference/operation-reconciliation/operation-reconciliation.md): Returns all registered operations for a given timeframe. - [Batch import of operations](https://api.amlyze.com/api-reference/operation/batch-import-of-operations.md) - [Evaluate operation](https://api.amlyze.com/api-reference/operation/evaluate-operation.md): To initiate the scoring process, the `sourceOfRiskLevel` field in the API payload must be set to `EVALUATE`. This instructs the AMLYZE engine to run the operation's data through the active risk matrix. In contrast, sending the value `IMPORT` will only update the operation's data in the system withou… - [Validate Batch Operations](https://api.amlyze.com/api-reference/operation/validate-batch-operations.md) - [Related entity adverse media screening completed](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-adverse-media-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Related entity adverse media screening pending](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-adverse-media-screening-pending.md): Fired when a related entity adverse media screening process is pending and human decision is needed. - [Related entity internal list screening completed](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-internal-list-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Related entity internal list screening pending](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-internal-list-screening-pending.md): Fired when a related entity internal list screening process is pending and human decision is needed. - [Related entity pep screening completed](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-pep-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Related entity pep screening pending](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-pep-screening-pending.md): Fired when a related entity PEP screening process is pending and human decision is needed. - [Related entity sanctions screening completed](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-sanctions-screening-completed.md): Fired when on completion by a human decision/automatically resolution. - [Related entity sanctions screening pending](https://api.amlyze.com/api-reference/related-entity-screening/related-entity-sanctions-screening-pending.md): Fired when a related entity sanctions screening process is pending and human decision is needed. - [Simplified customer import](https://api.amlyze.com/api-reference/simplified-customer/simplified-customer-import.md): This section provides information on how to generate a Simplified Customer for individuals or organizations. - [Account](https://api.amlyze.com/pages/account.md): Learn about Account resource - [Architecture](https://api.amlyze.com/pages/architecture.md) - [Access & Security](https://api.amlyze.com/pages/authorization.md): Access to the API service is secured through a multi-layer approach: network-level IP Access Control Lists (ACL) and application-level Token Authorization. Both mechanisms are required for successful requests. - [Business Unit](https://api.amlyze.com/pages/business_unit.md): Learn about Business Unit - [Communication Number](https://api.amlyze.com/pages/communication_number.md): Communication number unique identifier - [Contract](https://api.amlyze.com/pages/contract.md): Learn about Contract resource - [Customer](https://api.amlyze.com/pages/customer.md): Learn about Customer resource - [Importing Data](https://api.amlyze.com/pages/data_import.md): Learn how to import data into AMLYZE - [Data Lifecycle & Risk Evaluation](https://api.amlyze.com/pages/data_lifecycle.md): Manage the creation and modification of customer data. - [Errors](https://api.amlyze.com/pages/errors.md): Introduction to Errors - [Introduction](https://api.amlyze.com/pages/introduction.md) - [Operation](https://api.amlyze.com/pages/operation.md) - [Risk Management Categories](https://api.amlyze.com/pages/risk_management_category.md): A Guide to Customer and Operation Segmentation - [Webhooks](https://api.amlyze.com/webhooks/webhook.md) ## OpenAPI Specs - [openapi_webhooks](https://api.amlyze.com/webhooks/openapi_webhooks.json) - [openapi_api_adapter](https://api.amlyze.com/api/openapi_api_adapter.json) - [openapi_integrations](https://api.amlyze.com/api/openapi_integrations.json) - [openapi_classifiers](https://api.amlyze.com/api/openapi_classifiers.json) - [openapi](https://api.amlyze.com/api-reference/openapi.json)