Get an RFI
Retrieve a single RFI by its UUID, with its items nested. The RFI must belong to you.
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.
Response
Success.
A request for information — one need, with its items nested. client_uuid (tenancy — you already are the client) and created_by / returned_by (which Kira analyst acted) are never echoed.
The subclient this RFI is about.
pending — it's your turn (unanswered items remain, or one was returned). answered — you answered everything; Kira is reviewing. resolved — Kira confirmed the need satisfied, terminal; always an act on the whole RFI, never inferred from its items. not_resolved — closed without resolving, terminal; see resolution_reason. A withdrawn RFI never appears here — it 404s instead.
pending, answered, resolved, not_resolved What this RFI is anchored to, or null when it's about the subclient directly (not a specific transaction). There is no virtual-account or capability anchor — an RFI never names which account is blocked.
- Option 1
- Option 2
Set only when status is not_resolved.
expired, rejected, null When you first handed back a response. Measures the hand-off to Kira, not when your subclient actually answered — the gap between the two is invisible to this API.
When this need was last answered. Moves on every answer round; a return that walks status back to pending doesn't touch it.
Set for all three closed outcomes — resolved, not_resolved, withdrawn — dating whichever occurred.