> ## Documentation Index
> Fetch the complete documentation index at: https://ekacare-durgesh-output-language.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

A unique identifier assigned to each consent request.

**Consent Artefacts**

Consent artefacts are generated upon the approval of consents.
Multiple consent artefacts can exist for a single consent, each corresponding to different providers.
These artefacts represent the linkage between a healthcare provider (HIP) and care contexts.

Upon receiving a consent request, users can approve or deny the request.
Additionally, they can revoke consent given for older requests.

<Note> User Authorization will be required for all these operations.</Note>

### Consent Management: Approve, Deny, or Revoke Requests

<Steps>
  <Step title="Approve Consent Request">
    Use the [Consent Approval](/api-reference/user-app/abdm-connect/consents/consent-approve) endpoint to approve a
    consent request. You will need to provide necessary consent, care contexts and hip details to process the approval.
  </Step>

  <Step title="Deny Consent Request">
    Use the [Consent Deny](/api-reference/user-app/abdm-connect/consents/consent-deny) endpoint to deny a consent request.
    Consent id and a proper reason with be required to deny the consent request.
  </Step>

  <Step title="Revoke Consent Request">
    Use the [Consent Revoke](/api-reference/user-app/abdm-connect/consents/consent-revoke) endpoint to revoke an existing consent.
    Consent Artefact Id will be need to revoke the consent for particular hip.
  </Step>
</Steps>