Remove one file
Take one file out of the item’s set. Explicit rather than implied by an upload, and recorded the same way: the set that still had it stays readable in the RFI’s history.
The last file cannot be removed — an item cannot read answered with nothing to review, so that is a 422. To swap the only file, upload the replacement first and then remove this one.
Authorizations
Access token from POST /auth (the data.access_token value).
API key issued by Kira. Required on every request, including /auth.
Headers
Optional. The date-versioned API version to apply for this request (e.g. 2026-04-14). When sent it always wins, even over your pinned account default. When omitted, the API uses your account's pinned version if set, otherwise a baseline default.
"2026-06-01"
Path Parameters
RFI UUID.
Item UUID. The item must be a document item of this RFI.
The file's own id, as returned in documents[].
Response
The file was removed; the item comes back with the shorter set.
The item after the change, in the same shape every read of it returns — so the whole resulting set of files and the item's status come back together.
One thing being asked for. The addressable unit of an RFI — a PATCH or a document upload always names an item_id, never the parent RFI.