# Fetch an RFI

Returns the full detail of a single RFI, including its status, the documents required to resolve it, the instructions to follow, and any reviewer or uploader comments. The RFI is looked up by its `id` (starting with `rfi_`), exposed on the underlying resource (for example the `rfi` object on a Payment) or in the [List RFIs](/api-documentation/apis/openapi/rfi/getrfis) response.
An RFI belonging to a different business, or an unknown `id`, returns `404` — the response does not distinguish the two, so RFI existence is not leaked.

Endpoint: GET /rfis/{id}
Version: 1.0.0
Security: JWT

## Path parameters:

  - `id` (string, required)
    The unique identifier of the RFI to fetch. Starts with `rfi_`.

## Response 200 fields (application/json):

  - `id` (string)
    The unique identifier for the RFI.
    Example: rfi_6a7c5018ZGuKP

  - `business_id` (string)
    The unique identifier of the business the RFI belongs to.
    Example: merch_685bb99eFhPGA

  - `entity_type` (string)
    The type of the underlying resource the RFI was raised against, for example `Payment`, `Payin`, `Payout`, `Refund`, `Order`, `Subscription` or `Chargeback`.
    Example: Payment

  - `entity_id` (string)
    The unique identifier of the underlying resource the RFI was raised against.
    Example: payt_6a7c50089mMiB

  - `status` (string)
    The current status of the RFI. `action_required` means documents are still owed — respond using [Respond to an RFI](/api-documentation/apis/openapi/rfi/respondrfi). `under_review` means documents have been submitted and are pending a decision. The final decision (`approved` or `rejected`) is communicated via webhook.
    Enum: "action_required", "under_review", "approved", "rejected", "superseded", "expired"

  - `created_at` (string)
    Timestamp representing when the RFI was created.
    Example: 2026-08-12T10:51:04.747Z

  - `updated_at` (string)
    Timestamp representing when the RFI was last updated.
    Example: 2026-08-13T06:42:00.878Z

  - `documents_required` (array)
    The documents needed to resolve this RFI. Submit documents against a specific requirement using its `rfi_doc_id` via the [Respond to an RFI](/api-documentation/apis/openapi/rfi/respondrfi) endpoint. Empty when the RFI does not require documents.

  - `documents_required.rfi_doc_id` (string)
    The unique identifier for this document requirement.
    Example: rfidoc_6a72a39b38jDD

  - `documents_required.description` (string)
    A human-readable description of what document is needed.
    Example: Last 3 months bank statement

  - `documents_required.multiple_allowed` (boolean)
    Whether more than one document can be submitted for this requirement.
    Example: true

  - `documents_required.max_count` (integer)
    The maximum number of documents that can be submitted for this requirement.
    Example: 3

  - `instructions` (string)
    Human-readable guidance on what is required to resolve the RFI. Falls back to a generic message when no specific instructions were set.
    Example: Upload your latest bank statement

  - `review_comments` (string | null)
    Comments left by the reviewer, for example why a previous submission was rejected. `null` when there are none.
    Example: Please re-upload a clearer copy.

  - `uploader_comments` (string | null)
    The note recorded against the RFI when documents were last submitted. `null` when there are none.
    Example: Uploaded the statement.

## Response 404 fields (application/json):

  - `error` (string)
    Enum: "Not found"

  - `message` (string)
    Entity not found
    Enum: "Entity not found"