# Custodian auth flows

A custodian auth flow defines the onboarding requirements for a
specific custodian — which files must be uploaded, what consent
types are supported, etc. Each custodian may have multiple flows.

The flow's `expectedFiles` drives the `pendingFiles` array on a
custodian-authority before consent can be submitted.

## Endpoints

GET /v2/custodian-auth-flows
  List all available custodian auth flows.

GET /v2/custodian-auth-flows/:id
  Fetch one auth flow.

## Path params

  id (required) — Auth-flow identifier (e.g. "nordea-20260630").

## Attributes (`type: custodian-auth-flow`)

  expectedFiles         (array) — Files required during onboarding. Each entry:
                                    name        (string) — e.g. "power-of-attorney"
                                    description (string)
                                    fileType    (string) — e.g. "pdf"
  supportedConsentTypes (array) — Subset of: "all", "specific".

## Relationships

  custodian — The custodian the flow belongs to.