On this page

Legacy wallet check with transaction reference

POST /api/v1/transaction-screenings is retained for existing integrations. It screens the counterparty wallet address at your organisation's Wallet Screening rate and stores your transaction hash as Myaza context. The hash is not sent to the wallet provider and is not analysed on-chain. For a new integration, use On-Demand Wallet Screening to check an address or Transaction Monitoring for a complete transaction decision.

shell

curl -X POST "https://sandbox.trust.myaza.app/api/v1/transaction-screenings" \
  -H "Authorization: Bearer $MYAZA_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: tx-wallet-check-123" \
  -d '{"network":"ethereum","transactionHash":"0xcccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc","direction":"outbound","counterpartyAddress":"0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","sandboxScenario":"wallet.sanctions.1_hop"}'

For outbound transfers, counterpartyAddress is the destination. For inbound transfers, it is the sender; depositAddress is optional context for your receiving wallet. asset is separate from the blockchain. The API key selects Sandbox or Production. Validation failures return 422 before a provider call or billable usage.

Read the result with GET /api/v1/transaction-screenings/{id}. Its transaction.hash is the reference you provided; risk, exposures, decision and rulesTriggered describe the screened wallet. The report route exports that saved Myaza decision. A full transaction risk assessment, alerts and monitoring lifecycle belong to Transaction Monitoring.