# Get subjects

URL: https://docs.hanzo.ai/docs/openapi/compliance/get-compliance-subjects-by-id

> Returns one subject WITH its contact PII — the only surface that returns it, and only to the owning org.

`GET /v1/compliance/subjects/{id}`

> [Compliance →](https://docs.hanzo.ai/docs/openapi/compliance) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                                    |
| ------------- | -------------------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/compliance/subjects/{id}` |
| **Method**    | `GET`                                              |
| **Operation** | `get_compliance_subjects_by_id`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`             |

Returns one subject WITH its contact PII — the only surface that
returns it, and only to the owning org. The response is never cached by any
intermediary.

## Request

1 field.

| Field | In   | Type   | Required | Description                               |
| ----- | ---- | ------ | -------- | ----------------------------------------- |
| `id`  | path | string | yes      | ID is the subject to read, from the path. |

## Response

| Status    | Body               | Meaning |
| --------- | ------------------ | ------- |
| `200`     | compliance.Subject | ok      |
| `default` | problem-details    | refused |

`200` body — 8 fields.

| Field       | In   | Type            | Always | Description                                                                                                                                    |
| ----------- | ---- | --------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| `createdAt` | body | integer (int64) | —      | CreatedAt is when the subject was first recorded, Unix SECONDS.                                                                                |
| `email`     | body | string          | —      | Email is the party's address, when the org supplied one.                                                                                       |
| `id`        | body | string          | —      | ID is the opaque handle every other record uses to point at this party.                                                                        |
| `kind`      | body | string          | —      | Kind is what is being verified: "individual" (a natural person, so KYC) or "business" (a legal entity, so KYB).                                |
| `name`      | body | string          | —      | Name is the party's name, under the same PII rule as Email.                                                                                    |
| `org`       | body | string          | —      | Org is the tenant that is doing the verifying — the party who must answer for this record, not the party being verified.                       |
| `ref`       | body | string          | —      | Ref is the org's OWN identifier for this party, carried so a caller can match a subject back to their system without keeping a second mapping. |
| `updatedAt` | body | integer (int64) | —      | UpdatedAt is when the subject's own fields last changed, Unix seconds.                                                                         |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo compliance subjects get <id>
```

**SDK**

**.ts**

```ts
import { Configuration, ComplianceApi } from 'hanzoai';

const api = new ComplianceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getComplianceSubjectsById({ id: 'id' });
```

**.py**

```python
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ComplianceApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ComplianceApi(client).get_compliance_subjects_by_id(id='id')
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ComplianceAPI.GetComplianceSubjectsById(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::apis::{configuration::Configuration, compliance_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = compliance_api::get_compliance_subjects_by_id(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ComplianceApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ComplianceApi(client).getComplianceSubjectsById();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/compliance/subjects/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **compliance** through the `compliance` tool, which names its 16 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_compliance_accreditation"
         }
       }
     }'
```

---

[Compliance API](https://docs.hanzo.ai/docs/openapi/compliance) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)