> ## Documentation Index
> Fetch the complete documentation index at: https://docs.humanos.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Requests

> How your organization collects authorizations from users.

## How it works

1. **Request configuration.** To create a request you must set:

* **Content**: approvals, workflows, actions, or an on-demand PDF
* **Contacts**: one or more users who will receive the request.
  > Requests containing approvals with document placements or forms are limited to a single contact to guarantee integrity. On-demand PDFs with placements support multiple contacts since placements are assigned per user without overlap.
* **Security level**: the minimum identity verification required to open the link

2. **User notification.** Each contact receives a message with a one-time passcode, or OTP, that unlocks a unique, non-shareable link inside Humanos. There they can review all the requested information and choose to accept or reject.
3. **Draft phase.** While contacts are deciding, the credential is in **Draft** status. Every action triggers a **webhook notification** so your systems can track progress in real time.
4. **Finalization.** Once all contacts have responded, or the expiry passes, the credential is finalized and permanently sealed.

**Notes**: Humanos sets a default expiry of 30 days for requests. A request must contain at least one approval or have security level set to Humanos Revalidation.

## Features

* **Create**: Configure a request for one or more contacts.
* **Cancel**: Immediately disables all contact links, preventing any further actions and cancels all the credentials in the request.

## Glossary

**Security Level**

When a user enters a secure request link, their current identity level is compared against the required security level, forcing a Humanos KYC process if it falls below the requirement.

* *Contact*: OTP only, no identity check
* *Organization KYC*: Forces a KYC process if the user does not have an identity.
* *Humanos KYC*: Forces a KYC process if the user does not have a Humanos verified identity.
* *Humanos Revalidation*: Always forces a KYC process.

**Note**: Check [Identity Levels](/essentials/introduction#identity-levels) for more information.

**Status**

* *Draft*: awaiting decisions from one or more contacts
* *Active*: all contacts accepted; credential is permanently sealed
* *Rejected*: at least one contact rejected; credential is permanently sealed
* *Expired*: expire date reached before all users decided; credential is permanently sealed
* *Cancelled*: manually cancelled; credential is permanently sealed

## API access

Everything on this page can be driven programmatically: create requests with [`POST /request`](/api-reference/latest/requests/create-request), list and inspect them with [`GET /request`](/api-reference/latest/requests/list-requests), cancel with `DELETE /request/{requestId}`, and resend an OTP with `PATCH /request/resend/{requestId}`. Outcomes arrive on your [webhook endpoint](/essentials/webhooks-intro).