# Requirement

The **Requirements** object represents personal details requested by the initiator during an activity. The recipient (receptor) determines which details to share to complete the activity.

### Fields

<table data-full-width="true"><thead><tr><th width="199">Field</th><th width="194">Type</th><th width="587">Description</th></tr></thead><tbody><tr><td><code>code</code></td><td><code>string</code></td><td>Unique identifier for this requirement.</td></tr><tr><td><code>type</code></td><td><code>string</code></td><td>Specifies the type of requirement.</td></tr><tr><td><code>category</code></td><td><code>string</code></td><td>Category of the requirement.</td></tr><tr><td><code>data</code></td><td><code>object</code></td><td>Contains personal details for requirements involving data sharing.<br><strong>Note:</strong> This field appears only in the <code>accepted_requirements</code> array within the Activity object.</td></tr><tr><td><code>items</code></td><td><code>array</code></td><td><p>Contains a detailed list of personal details involving grouped requirements. Examples include:</p><ul><li><code>IDENTITY TRUST</code> = <code>"RQ_002"</code></li><li><code>PERSONAL INFO</code> = <code>"RQ_004"</code></li><li><code>IDENTITY DOCUMENT</code> = <code>"RQ_006"</code></li></ul><p><strong>Note:</strong> Refer to the <strong>Requirement Item</strong> table for structure details.</p></td></tr></tbody></table>

## Requirement Item

The **Requirement Item** object represents detailed sub-requirements within a larger group of personal details requested during an activity.

<table data-full-width="true"><thead><tr><th width="199">Field</th><th width="195">Type</th><th width="567">Description</th></tr></thead><tbody><tr><td><code>code</code></td><td><code>string</code></td><td>Unique code identifying this specific inner requirement</td></tr><tr><td><code>type</code></td><td><code>string</code></td><td>Specifies the type of sub-requirement.</td></tr><tr><td><code>data</code></td><td><code>object</code></td><td><p>Contains a detailed list of personal details associated with grouped requirements.<br>Examples include:</p><ul><li><code>IDENTITY TRUST</code> = <code>"RQ_002"</code></li><li><code>PERSONAL INFO</code> = <code>"RQ_004"</code></li><li><code>IDENTITY DOCUMENT</code> = <code>"RQ_006"</code></li></ul><p><strong>Note:</strong> This field appears only in the <code>accepted_requirements</code> array within the Activity object.</p></td></tr></tbody></table>

This structure allows for a more granular breakdown of individual requirements, ensuring clarity and flexibility during implementation.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-business.mio.id/api-reference/data-dictionary/objects/requirement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.