Answer 1 to N items
Answer one or more items of the RFI in a single call — each element of items[] names its own item_id. This is still per-item: each named item gets its own transition and its own event; what you avoid is one round-trip per item for what was, for you, one action (fill the form, submit).
Marks each item answered on receipt — not when anything downstream accepts it. All-or-nothing: every item in the batch is validated against its own answer_spec before any of them is written; if one fails, the whole call returns 422 naming which, and the server is left exactly as it was.
Answering a returned item is answering it again with the same item_id — a returned item is still pending, carrying a review_note, and there is no successor RFI or item to discover. A document item is never answered here; upload files to it instead (see the document endpoints below). Partial answers are the normal case, not an edge case: answering item 1 and 3 and leaving item 2 is expected.
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.
Body
1 to N items to answer in one call, each naming its item_id. Validated against every named item's answer_spec before anything is written: if any entry fails, the whole batch is rejected with 422 and the server is left exactly as it was. A document item is never answered here — upload files to it instead.
1Response
All named items were valid and are now answered.
The items named in the request, each reflecting the write (status: "answered", answer_value/documents, updated_at).