> For the complete documentation index, see [llms.txt](https://docs.vcheckglobal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vcheckglobal.com/api-reference/common-endpoints/subjects.md).

# Subjects

All subjects on the account across all products.

## List All Subjects

> Returns the list of all subjects associated with the account.\
> \
> \*\*Pagination:\*\* Fixed 50 records per page. Pass \`?page=N\` to navigate. Stop when \`next\` is \`null\`.\
> \
> \### Response fields\
> \
> \| Field | Type | Description |\
> \|-------|------|-------------|\
> \| \`subject\_id\` | integer | Unique subject identifier |\
> \| \`first\_name\` | string | Subject's first name (Individual) |\
> \| \`middle\_name\` | string | Subject's middle name |\
> \| \`last\_name\_entity\` | string | Last name (Individual) or entity name (Entity) |\
> \| \`subject\_type\` | string | \`Individual\` or \`Entity\` |\
> \| \`monitoring\_status\` | string | \`On\` (at least one active subscription) or \`Off\` |<br>

```json
{"openapi":"3.1.0","info":{"title":"Vcheck Global API","version":"5.4.0"},"tags":[{"name":"Subjects","description":"All subjects on the account across all products."}],"servers":[{"url":"https://api-platform.vcheckglobal.net/v2","description":"Vcheck platform (sandbox host issued first; production host after sign-off)"}],"security":[{"bearerAuth":[]}],"components":{"securitySchemes":{"bearerAuth":{"type":"http","scheme":"bearer","bearerFormat":"JWT","description":"Obtain a token via POST https://api-platform.vcheckglobal.net/v2/oauth2/token.\nInclude in all subsequent requests as `Authorization: Bearer <token>`.\nTokens expire after 3,600 seconds - cache and reuse; request a new one only when close to expiry.\n"}}},"paths":{"/subjects":{"get":{"tags":["Subjects"],"operationId":"getAllSubjects","summary":"List All Subjects","description":"Returns the list of all subjects associated with the account.\n\n**Pagination:** Fixed 50 records per page. Pass `?page=N` to navigate. Stop when `next` is `null`.\n\n### Response fields\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `subject_id` | integer | Unique subject identifier |\n| `first_name` | string | Subject's first name (Individual) |\n| `middle_name` | string | Subject's middle name |\n| `last_name_entity` | string | Last name (Individual) or entity name (Entity) |\n| `subject_type` | string | `Individual` or `Entity` |\n| `monitoring_status` | string | `On` (at least one active subscription) or `Off` |\n","parameters":[{"name":"page","in":"query","required":false,"description":"Page number to retrieve (1-indexed, default: 1). Each page returns up to 50 records.","schema":{"type":"integer"}}],"responses":{"200":{"description":"Subjects retrieved successfully.","content":{"application/json":{"schema":{"type":"object","properties":{"count":{"description":"Total number of records across all pages.","type":"integer"},"next":{"description":"Full URL to the next page. null on the last page.","type":["string","null"]},"previous":{"description":"Full URL to the previous page. null on the first page.","type":["string","null"]},"results":{"description":"Array of records for the current page (max 50).","type":"array","items":{"type":"object","properties":{"subject_id":{"description":"Unique subject identifier.","type":"integer"},"first_name":{"description":"First name of the subject. null for entities.","type":["string","null"]},"middle_name":{"description":"Middle name of the subject. May be empty or null.","type":["string","null"]},"last_name":{"description":"Last name for individuals, or entity name for organizations.","type":["string","null"]},"full_name":{"description":"Computed full name of the subject (first + last name).","type":["string","null"]},"subject_type":{"description":"Whether the subject is a person or an organization.","type":"string","enum":["Individual","Entity"]},"monitoring_status":{"description":"Current monitoring status - 'On' if the subject has an active monitoring subscription, 'Off' otherwise.","type":"string","enum":["On","Off"]}}}}}}}}},"403":{"description":"Forbidden - missing or invalid Client-ID credentials, insufficient scope, endpoint disabled via feature flag, or authenticated client has no linked account. Verify the scopes assigned to your credentials.","content":{"application/json":{"schema":{"type":"object","properties":{"detail":{"description":"Authorization or access error message.","type":"string","default":"This endpoint is currently disabled."}}}}}},"500":{"description":"Internal server error - an unexpected error occurred. Please try again later or contact support if the issue persists.","content":{"application/json":{"schema":{"type":"object","properties":{"detail":{"description":"Internal server error message.","type":"string","default":"An unexpected error occurred while processing the request."}}}}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vcheckglobal.com/api-reference/common-endpoints/subjects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.