> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/ja/api-documentation/transaction-screening/batch-screen-transactions.md).

# トランザクションを一括スクリーニングする

トランザクションの一括リスクスクリーニングは、非同期タスクとして実行されます。各トランザクションには一意のTask IDが割り当てられ、ユーザーはタスクAPIを通じて詳細な結果を取得できます。

## Screen multiple transactions

> Submit a batch transaction screening task and return task IDs.

```json
{"openapi":"3.0.0","info":{"title":"Compliance API","version":"2.0.0"},"tags":[{"name":"Transaction Screen","description":"Transaction screening and retrieval APIs."}],"servers":[{"url":"https://api.blocksec.com/phalcon/compliance/v2","description":"Production server"}],"security":[{"API-Key":[]}],"components":{"securitySchemes":{"API-Key":{"type":"apiKey","in":"header","name":"API-Key"}},"schemas":{"TransactionScreen":{"type":"object","required":["chainId","hash","direction","toAddress"],"properties":{"chainId":{"type":"integer","description":"The chain ID. For all supported chains and corresponding chain IDs, see [https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/supported-chains](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/supported-chains)."},"hash":{"type":"string","description":"The transaction hash."},"direction":{"type":"string","enum":["deposit","withdrawal","both"],"description":"The direction of the transaction."},"toAddress":{"type":"string","description":"The user’s deposit address (for deposits) or withdrawal address (for withdrawals)."},"transferIndex":{"type":"integer","description":"The index of the transfer within the transaction. Optional; used to identify a specific transfer if direction and toAddress are not unique. For BTC transactions, this field represents the toAddressIndex. If omitted and multiple transfers match, the first transfer will be used."},"includeDetails":{"type":"boolean","deprecated":true,"description":"Deprecated. Whether to include the legacy riskDetail field on every alert. Defaults to false."}}},"ErrorCodeMsg":{"properties":{"code":{"type":"integer","description":"The business status code. `0` means the request succeeded; any other value means it failed. Business errors are returned with HTTP 200 and a non-zero code, so a 200 response is not by itself a success — always check this field. Authentication and rate-limiting failures use a non-200 HTTP status instead, so check both. For all codes and their messages, see [https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/error-messages](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/error-messages)."},"msg":{"type":"string","description":"`\"Success\"` when `code` is 0, otherwise the error message for that code."}}},"TransactionTasksResult":{"type":"object","properties":{"taskIds":{"type":"array","description":"The list of task IDs.","items":{"type":"string","description":"The unique identifier for the task."}}}}}},"paths":{"/transactions/screen":{"post":{"tags":["Transaction Screen"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","properties":{"transactions":{"type":"array","minItems":1,"maxItems":50,"items":{"$ref":"#/components/schemas/TransactionScreen"},"description":"The list of transactions to be screened. Provide between 1 and 50 transactions per request."}}}}}},"responses":{"200":{"description":"Response. A non-zero `code` indicates a business error even when the HTTP status is 200.","content":{"application/json":{"schema":{"type":"object","properties":{"code":{"$ref":"#/components/schemas/ErrorCodeMsg/properties/code","description":"The status code of this request. For all possible codes and corresponding errors/messages, see [https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/error-messages](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/error-messages)."},"msg":{"$ref":"#/components/schemas/ErrorCodeMsg/properties/msg","description":"The message of this request. For all possible codes and corresponding errors/messages, see [https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/error-messages](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/error-messages)."},"data":{"$ref":"#/components/schemas/TransactionTasksResult"}}}}}},"401":{"description":"Authentication failed. The `API-Key` header is missing or invalid."},"429":{"description":"Rate limit exceeded. Reduce the request rate and retry."}},"description":"Submit a batch transaction screening task and return task IDs.","summary":"Screen multiple transactions"}}}}
```
