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

# Step 5c — Get Status and Validity of Latest Screening

This endpoint returns the **status and validity** of the latest screening for a given **Primary Customer**.

It provides three crucial keys:

* **`concluded`** — final outcome of the screening process (e.g., whether the result indicates a sanction hit, a PEP hit, or no hits at all).
* **`screeningValid`** — a boolean indicating whether the screening result is valid. This will be `true` unless system errors prevent proper screening.
* **`screeningStatus`** — the current state of the screening process, useful for polling until the screening has finished.

## Path Parameter

* **`customerId`** — This must be the **Primary Customer's ID**.

## Example Request

```bash theme={null}
curl -X POST "{{backend_url}}/api/customer/{{customerId}}/screen/status" \
  -H "Authorization: Bearer <token>" \
  -H "X-Domain-ID: {{domain_id}}"
```

## Example Success Responses

### ✅ Screening Completed and Valid

Below is the following sample JSON response body when it is successful in polling for the validity of the latest screening, which the screening has been completed and it is considered as a valid screening.

```json theme={null}
{
  "concluded": false,
  "screeningValid": true,
  "screeningStatus": "DONE"
}
```

### ⏳ Screening Still Pending

Below is the following sample JSON response body when it is successful in polling for the validity of the latest screening, which the server is still trying to ascertain if the system has completed its screening.

```json theme={null}
{
  "concluded": false,
  "screeningValid": false,
  "screeningStatus": "PENDING"
}
```

## Notes

This endpoint is useful for polling the system to check when a screening has finished.

Once screeningStatus is DONE and screeningValid is true, you can rely on the concluded field for the final outcome.

Typical screening statuses may include: PENDING, IN\_PROGRESS, DONE, or FAILED.


## OpenAPI

````yaml GET /api/customer/{customerId}/screen/status
openapi: 3.1.0
info:
  description: Api Documentation
  version: '3.0'
  title: Api Documentation
  termsOfService: urn:tos
  contact: {}
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0
servers:
  - url: https://api.artemis.cynopsis.co
security: []
tags:
  - name: app-config-controller
    description: App Config Controller
  - name: asia-verify-controller
    description: Asia Verify Controller
  - name: authentication-controller
    description: Authentication Controller
  - name: authentication-manager-controller
    description: Authentication Manager Controller
  - name: basic-error-controller
    description: Basic Error Controller
  - name: comment-controller
    description: Comment Controller
  - name: customer-controller
    description: Customer Controller
  - name: dashboard-controller
    description: Dashboard Controller
  - name: domain-controller
    description: Domain Controller
  - name: expiring-document-controller
    description: Expiring Document Controller
  - name: hand-shake-controller
    description: Hand Shake Controller
  - name: media-controller
    description: Media Controller
  - name: on-going-due-diligent-controller
    description: On Going Due Diligent Controller
  - name: own-restricted-list-controller
    description: Own Restricted List Controller
  - name: periodic-review-controller
    description: Periodic Review Controller
  - name: quick-scan-controller
    description: Quick Scan Controller
  - name: user-controller
    description: User Controller
paths:
  /api/customer/{customerId}/screen/status:
    get:
      tags:
        - customer-controller
      summary: getScreeningStatus
      operationId: getScreeningStatusUsingGET
      parameters:
        - name: customerId
          in: path
          description: customerId
          required: true
          schema:
            type: integer
            format: int64
        - name: X-Domain-ID
          in: header
          description: X-Domain-ID
          required: true
          schema:
            type: integer
            format: int64
      responses:
        '200':
          description: OK
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/CustomerScreeningStatusResponseDto'
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Not Found
      security:
        - OAuth2_Client_Credentials: []
        - OAuth2_Password: []
components:
  schemas:
    CustomerScreeningStatusResponseDto:
      type: object
      properties:
        concluded:
          type: boolean
        screeningStatus:
          type: string
          enum:
            - DONE
            - FAILED
            - NEVER
            - PENDING
        screeningValid:
          type: boolean
      title: CustomerScreeningStatusResponseDto
  securitySchemes:
    OAuth2_Client_Credentials:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://crm.cynopsis.co/oauth/token
          scopes: {}
    OAuth2_Password:
      type: oauth2
      flows:
        password:
          tokenUrl: https://crm.cynopsis.co/oauth/token
          scopes: {}

````