---
title: Request documents from an applicant
description: Send an applicant one link. They open it on a phone, with no sign-in, and add each document the case asks for under the requirement it answers.
section: Filing and documents
order: 9
---

On a case's **Intake** tab, choose **Copy request link** and send the link to the applicant. It works for 30 days.

## What the applicant sees

- **Your organization's logo,** and one section of the list at a time.
- **Each document asked for:** its name, the formats it takes, and how recent it must be. A required document has an asterisk.
- **Add file** under each document. A file that is added shows by its name, marked **filed**.
- **Save & continue** moves to the next section. The last screen lists the required documents that are still missing.

The applicant sees the documents your expected document list lets an applicant add: a section whose **Who adds** names the Applicant. See [expected document lists](/docs/concepts/expected-document-lists).

## What you get

- **Each file lands in the case under the requirement it answers,** as a file you add there yourself does.
- **The case's workflow runs on it,** when the case has one.
- **The ledger records the link's maker,** with `via: Request link`.

## What the link allows

- **Whoever holds the link** adds files to the documents it asks for and sees those documents' names and file names. Nothing else of the case shows.
- **It ends** after 30 days, when the person who made it is deactivated or changes their password, and when the key that made it is revoked.
- **A format the document does not take is refused,** and the page says which formats it takes.

## Your logo and colour

A Manager sets them under **Settings**, in **Logo and colour**.

- **The logo** is a PNG, JPEG, WebP or SVG file of 200 KB at most. Without one, the page shows Sheaf's mark.
- **The colour** draws the page's progress line. Give it as `#RRGGBB`, such as `#0B5FFF`.

## From the API

One call makes the link. Name the documents to ask for some of them only:

```sh
curl -X POST https://sheaf.us/api/applications/xK5UQ_ZxzV/request-links \
  -H "Authorization: Bearer $SHEAF_API_KEY" -H "Content-Type: application/json" \
  -d '{ "expectedDocIds": ["pay-stubs", "bank-statements"] }'
```

It answers `requestPath` and `expiresAt`. The applicant opens `https://sheaf.us` followed by `requestPath`.

From Claude, with Sheaf connected, ask: "Make a request link for the Jane Doe case, for her pay stubs and bank statements." See [Connect Claude](/docs/agents/connect-claude).