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 a worker. Worker identified by synthetic id (`worker.id = wkr_…`) or external id (`worker.externalId` + optional `sourceSystem`). `requestedCredentialTypes` is required and validated against the credential types catalogue.
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. Each entry takes the same body shape as `POST /fetch-requests` minus `worker` (which is supplied at the top level as a list). 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