> ## Documentation Index
> Fetch the complete documentation index at: https://developers.argosidentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GET Ongoing Monitoring Record

> Retrieve detailed information about a specific ongoing monitoring record by its unique identifier

<Info>
  This endpoint supports secure data transmission with AES-256 encryption when the option is enabled.
</Info>

## Endpoint

```bash theme={null}
GET /submission/aml/monitor/{worklistId}/{recordId}
```

## Base URL

```bash theme={null}
https://rest-api.argosidentity.com/v3/submission/aml/monitor
```

## Authentication

Include your API key in the request header:

<ParamField header="x-api-key" type="string" required>
  Your API key for authentication
</ParamField>

## Path Parameters

<ParamField path="worklistId" type="string" required>
  The ID of the worklist containing the record
</ParamField>

<ParamField path="recordId" type="string" required>
  The unique identifier of the ongoing monitoring record to retrieve
</ParamField>

## Request Example

<RequestExample>
  ```bash cURL theme={null}
  curl --location 'https://rest-api.argosidentity.com/v3/submission/aml/monitor/{worklistId}/{recordId}' \
  --header 'x-api-key: {yourAPIKey}'
  ```
</RequestExample>

## Response

### Success Response

<ResponseExample>
  ```json Success theme={null}
  {
      "name": "test",
      "id": "mes3uzetD55S_evcka62mes3ugzb_mg",
      "submissionId": "evcka62mes3ugzb_mg",
      "nationality": "KOR",
      "status": "screenedNoMatches",
      "dob": "1992-06-13",
      "email": "test@test.com",
      "memo": "",
      "tags": [],
      "admin": "yunjik@argosidentity.com",
      "updateTime": "2025-08-26T05:28:20.165Z",
      "openCount": 0,
      "falsePositiveCount": 0,
      "truePositiveCount": 0,
      "discardedCount": 0
  }
  ```
</ResponseExample>

### Response Fields

<ResponseField name="name" type="string" required>
  Full name of the person being monitored
</ResponseField>

<ResponseField name="id" type="string" required>
  Unique identifier for the ongoing monitoring record
</ResponseField>

<ResponseField name="submissionId" type="string" required>
  The submission ID associated with this record
</ResponseField>

<ResponseField name="nationality" type="string" required>
  Country code of the person's nationality (e.g., "KOR" for Korea)
</ResponseField>

<ResponseField name="status" type="string" required>
  Current screening status of the record (e.g., `screenedNoMatches`, `redFlag`, etc.). For detailed information about AML screening result codes, refer to the [AML Database Sources and Codes](/dashboard/en/aml-source) documentation.
</ResponseField>

<ResponseField name="dob" type="string" required>
  Date of birth in YYYY-MM-DD format
</ResponseField>

<ResponseField name="email" type="string">
  Email address of the person being monitored
</ResponseField>

<ResponseField name="memo" type="string">
  Administrative notes or comments about the record
</ResponseField>

<ResponseField name="tags" type="array">
  Array of tags associated with this record
</ResponseField>

<ResponseField name="admin" type="string" required>
  Email address of the administrator who last modified the record
</ResponseField>

<ResponseField name="updateTime" type="string" required>
  ISO 8601 timestamp of the last record update
</ResponseField>

<ResponseField name="openCount" type="number" required>
  Number of open matches found during screening
</ResponseField>

<ResponseField name="falsePositiveCount" type="number" required>
  Number of false positive matches identified
</ResponseField>

<ResponseField name="truePositiveCount" type="number" required>
  Number of confirmed positive matches
</ResponseField>

<ResponseField name="discardedCount" type="number" required>
  Number of discarded or invalid matches
</ResponseField>

### Error Response

<ResponseExample>
  ```json Error theme={null}
  {
      "errorCode": "invalid_record",
      "errorMessage": "Some records do not exist"
  }
  ```
</ResponseExample>

## Error Codes

| Error Code          | HTTP Status | Description                            |
| ------------------- | ----------- | -------------------------------------- |
| `invalid_record`    | 400         | The specified record ID does not exist |
| `invalide_worklist` | 400         | The specified worklist ID is invalid   |
| `invalid_project`   | 400         | Missing project ID or invalid API key  |

## Secure Data Transmission

<Note>
  This endpoint supports secure data transmission with AES-256 encryption when the option is enabled. The encryption/decryption method follows the same approach as other secure endpoints.
</Note>

## Related Endpoints

<CardGroup cols={2}>
  <Card title="Create Ongoing Monitoring Records" icon="plus" href="/api-reference/api-reference-guide/aml_data/aml-ongoing-monitoring/Post-Ongoing-Monitoring">
    Register new ongoing monitoring records for submissions
  </Card>

  <Card title="Delete Ongoing Monitoring Records" icon="trash" href="/api-reference/api-reference-guide/aml_data/aml-ongoing-monitoring/Delete-Ongoing-Monitoring">
    Remove ongoing monitoring records from the system
  </Card>
</CardGroup>