Skip to main content
Underwriters may create information requests when:
  • Automated processing identifies missing or inconsistent data
  • Manual underwriting review requires clarification
  • Additional documentation is needed to complete verification or risk assessment
Multiple information requests may be active at the same time for a single application.

​
Query information requests

Use the underwritingInformationRequests query to retrieve active and historical information requests for an application.
Filter by status to see only active (REQUESTED) information requests that require attention.
query UnderwritingApplicationWithInfoRequests($input: UnderwritingApplicationInput!) {
  underwritingApplications(input: $input) {
    items {
      id
      informationRequests(input: { where: { status: { eq: REQUESTED } }, paging: { skip: 0, take: 10 } }) {
        id
        applicationId
        status
        title
        description
        createdDateTime
        fulfilledDateTime
      }
    }
  }
}

{
  "data": {
    "underwritingApplications": {
      "items": [
        {
          "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
          "informationRequests": [
            {
              "id": "b2c3d4e5-f6a7-4b8c-9d0e-1f2a3b4c5d6e",
              "applicationId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
              "status": "REQUESTED",
              "title": "Proof of Address",
              "description": "Please provide proof of current business address",
              "createdDateTime": "2024-01-15T14:00:00Z",
              "fulfilledDateTime": null
            }
          ]
        }
      ]
    }
  }
}
Run in Playground

​
Webhooks

Information request lifecycle events are emitted via webhooks, allowing your system to receive real-time notifications when:
  • A new information request is created (status: REQUESTED)
  • An information request is fulfilled (status: FULFILLED)
Configure webhooks to automatically notify merchants or internal systems when information requests require attention.