# Data Elements
source: https://developer.mastercard.com/open-finance-data/documentation/tutorials-and-guides/data-elements-overview/index.md

## Overview {#overview}

The Consents API provides structured data elements that describe the lifecycle, ownership, and status of user consents used to authorize access to financial data. These fields allow partners to create consents, retrieve their current state, and manage access termination in a transparent and auditable way.

This section outlines the data elements returned by the Consents API when creating, retrieving, or managing consents.

## Consent Response Fields {#consent-response-fields}

This table lists the fields available in responses returned by the Consents API.

Before reviewing the fields, it is important to understand the following concept:

* **Consent Status** represents the current state of a consent within its lifecycle (for example, inactive, active, or revoked). The status determines whether access to financial data is permitted at a given point in time.

|     **Field**      | **Field Name** |                                                **Description**                                                |              **Example**               |
|--------------------|----------------|---------------------------------------------------------------------------------------------------------------|----------------------------------------|
| **Consent ID**     | `consentId`    | Unique identifier assigned to the consent. This ID is used to retrieve, manage, or revoke a specific consent. | `d4ed1ee2-bf8e-4611-8507-55f4c410ce25` |
| **End Users**      | `endUsers`     | List of end users associated with the consent. Currently, a single end user is supported per consent.         | `[ { ... } ]`                          |
| **Created At**     | `createdAt`    | Date and time when the consent was created in the system.                                                     | `2023-11-28T00:00:00.0000000+00:00`    |
| **Consent Status** | `status`       | Current status of the consent, indicating whether access to financial data is permitted or restricted.        | `INACTIVE`                             |

## Consent Response Fields {#consent-response-fields-1}

The following fields are required when creating a new consent.

|           **Field**           |      **Field Name**      |                                                        **Description**                                                        |              **Example**               |
|-------------------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|
| **Use Case Configuration ID** | `useCaseConfigurationId` | Identifier of the use case configuration assigned during onboarding. This value defines the scope and purpose of the consent. | `41b1452a-b091-4cac-a624-e599f3b416c6` |
| **End Users**                 | `endUsers`               | List of end users for whom the consent is being created. A single end user is supported.                                      | `[ { ... } ]`                          |