> 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/pt-br/api-documentation/account-management/get-screening-usage.md).

# Obter uso da triagem

## Get screening usage

> Get the account's screening usage count based on screen tasks. Optionally filter by a time range and a target type. If both startTime and endTime are omitted, the current billing cycle is used by default.

```json
{"openapi":"3.0.0","info":{"title":"Compliance API","version":"2.0.0"},"tags":[{"name":"Account","description":"Account-level APIs such as usage queries."}],"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":{"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."}}}}},"paths":{"/account/usage/screening":{"get":{"tags":["Account"],"description":"Get the account's screening usage count based on screen tasks. Optionally filter by a time range and a target type. If both startTime and endTime are omitted, the current billing cycle is used by default.","parameters":[{"name":"startTime","in":"query","required":false,"description":"Start of the time range, as a Unix timestamp in seconds (inclusive). If both startTime and endTime are omitted, the current billing cycle is used.","schema":{"type":"integer","format":"int64"}},{"name":"endTime","in":"query","required":false,"description":"End of the time range, as a Unix timestamp in seconds (inclusive). If both startTime and endTime are omitted, the current billing cycle is used.","schema":{"type":"integer","format":"int64"}},{"name":"target","in":"query","required":false,"description":"The target type to count. Omit to count all targets.","schema":{"type":"string","enum":["address","transaction"]}}],"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 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."},"msg":{"$ref":"#/components/schemas/ErrorCodeMsg/properties/msg","description":"`\"Success\"` when `code` is 0, otherwise the error message for that code."},"data":{"type":"object","properties":{"screeningCount":{"type":"integer","format":"int64","description":"The number of screen tasks that match the query."}}}}}}}},"401":{"description":"Authentication failed. The `API-Key` header is missing or invalid."},"429":{"description":"Rate limit exceeded. Reduce the request rate and retry."}},"summary":"Get screening usage"}}}}
```
