Fetch Requests
Compliance-maintenance asks sent to existing workers.
List fetch requests
Search fetch requests. Filter by `status`, `workerId`, or free-text query across worker name and email. Soft-deleted entries excluded by default.
Create fetch request
Send a new fetch request to an existing worker.
Re-send a fetch request
Generates a fresh token, extends `tokenExpiresAt`, resets status to INITIATED so the mail action picks it up.
Send a reminder email
Send a reminder email
Cancel a fetch request
Cancel a fetch request
Create fetch requests in bulk
Fan out one fetch request per worker in a single call. Top-level `requirements` (or legacy `requestedCredentialTypes`) is applied uniformly to every worker — exactly one of the two must be supplied. Per-worker overrides are not supported here; create individually if you need per-worker shaping. Returns per-worker results — partial failures don't roll back successful sibling creates. Capped at 50 workers per call.
Get fetch request
Fetch a single request by id.
Soft delete a fetch request
Soft delete a fetch request
Partially update a fetch request
Limited surface — only `message` and `expiryDays` are mutable. Status changes go through dedicated lifecycle endpoints; worker + requestedCredentialTypes are immutable.
List submitted credentials for a fetch request
List submitted credentials for a fetch request
Download screening results report (PDF)
Generates a PDF report of the verification outcomes for a fetch request. Available only once the request is COMPLETED (every requested verifiable has a result); returns 409 otherwise.