> For the complete documentation index, see [llms.txt](https://docs.corppass.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corppass.gov.sg/technical-specifications/corppass-authorization-api-fapi-2.0/integration-guide/4.-userinfo-endpoint/person-info.md).

# Person Info

The `person_info` claim provides **personal information** about the **user acting on behalf of the entity**.

{% hint style="info" %}
This claim is only returned in the [Userinfo Endpoint](/technical-specifications/corppass-authorization-api-fapi-2.0/integration-guide/4.-userinfo-endpoint.md) response when

1. [**Myinfo Business person scopes**](/technical-specifications/corppass-authorization-api-fapi-2.0/scopes/myinfo-business-scopes/person-scopes.md) are requested.
2. The digital service is a [**Myinfo Business application**](/products/myinfo-business.md).
   {% endhint %}

## `person_info` Attributes

Attributes in `person_info` are scope-driven.

Each attribute maps directly to a requested [Person Scope](/technical-specifications/corppass-authorization-api-fapi-2.0/scopes/myinfo-business-scopes/person-scopes.md) and will only be included in the response if that scope is present.

For the full set of attributes and their structures, refer to the **OpenAPI specifications**:

{% file src="/files/lXMe7LqYQSE4LGboBJ16" %}

Refer to [common attribute patterns](/technical-specifications/corppass-authorization-api-fapi-2.0/integration-guide/4.-userinfo-endpoint/entity-info.md#common-attribute-patterns) for some of the common attribute patterns.

## Sample Payload

<details>

<summary><code>person_info.name</code> attribute for the scope <code>user.name</code></summary>

```json
{
  "person_info": {
    "name": {
       "classification": "C",
       "lastupdated": "2019-03-26",
       "source": "1",
       "value": "TAN XIAO HUI"
    }
  }
}
```

</details>