> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review an underwriting result

> Understand every origination drawer tab: the risk package, captured request and response, supporting documents and connected sources.

Use **Origination** to review the underwriting your integration submits to Insights. Each record brings together the application inputs, processing state, risk package, documents and connected sources.

## Find and open an origination

Open **Origination** in the left navigation. Use the status views, filters and search to locate the borrower or request. Check the selected workspace and environment before searching for an identifier from your application.

![Origination table showing six fictional businesses with completed, requires-action and failed processing statuses.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/origination.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=1355e099dac7c4568e5a67b1abc8e5b8)

The origination table combines completed results with cases that need attention. These businesses are fictional.

Select a row to open its drawer. Confirm the borrower, origination identifier and environment in the header. The arrows move between records in the list; closing the drawer returns you to the table. **Copy record ID** helps you correlate the case with your own system or a support request.

| Tab | The question it answers |
| - | - |
| [Overview](#overview) | What did underwriting find, and what information supports it? |
| [API request](#api-request) | What inputs and references were captured for this run? |
| [API response](#api-response) | What does the returned origination record contain? |
| [Documents](#documents) | Which files are associated with this origination? |
| [Integrations](#integrations) | Which borrower connections are associated with this origination? |

> [!NOTE]
>
> **API request** and **API response** are visible to Owners and Developers. Analysts use Overview, Documents and Integrations. Number badges count associated records, not completed checks or a guarantee of complete evidence.

## Overview

Start here for a readable review of the result. The summary identifies the borrower, product, requested amount and risk policy when supplied. Scroll through the drawer to inspect:

* **Risk package:** the available underwriting result and its supporting dimensions. Expand nested sections to read their values, coverage and qualifications.
* **Request information** and **Underwriting inputs:** the application facts used for this run, such as requested financing and declared business information.
* **Borrower information:** the subject of the assessment and its recorded attributes.
* **Published evidence** and **Activity:** associated published records and recorded activity when available. Open an evidence row for further detail.

![Evergreen Outdoor Supply Ltd origination drawer with Overview selected, a within-policy risk package and application information.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/origination-drawer.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=7fe1f0c60cdce8ea48dc04c11ca37dff)

Overview brings the readable risk package and its inputs together. Scroll within the drawer for evidence and additional sections.

For example, review Evergreen Outdoor Supply's requested amount alongside its policy result, then compare the declared application information with the evidence used. A missing risk package means there is no published result to review here; it is not a decline. An absent metric is not zero.

## API request

Use this tab when investigating unexpected results or checking what your integration submitted. Inspect the captured payload for the borrower, application facts, document and connection identifiers, and lending-product and risk-policy version references.

![Origination API request tab showing a captured JSON payload, credentials-redacted notice and Download JSON control.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/origination-api-request.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=9b38cae0047ac5143d106c66e73b8b4f)

The captured request view supports technical inspection and JSON download. Check the submitted inputs within the payload.

Captured record metadata can surround the submitted inputs. In this example, those inputs are under `submitted_request`. Do not use the entire displayed record as a new POST request: use [Data Lookup](https://docs.amlok.io/console/data-lookup.md) to check the endpoint's request fields and required structure.

Use the copy control or **Download JSON** to inspect the payload locally. **Related API requests** lists linked request logs when available. If that list is empty, search [Request logs](https://docs.amlok.io/console/request-logs.md) using the identifiers you have; an empty relationship list does not prove that no request was sent. Opening or downloading the captured request does not submit it again.

## API response

Use this tab to understand the returned origination record and compare it with your application's handling of the result.

![Origination API response tab displaying the completed origination resource, associated identifiers and Download JSON control.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/origination-api-response.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=feb3654abe9f8ff1f02af2d0f6da21cf)

The response identifies the origination's state and associated result. A risk package reference can point to a separately retrieved package.

Check the resource identifier, processing `status`, timestamps and `record_version`. Inspect `failure` or `requirements` when present, and follow the `risk_package_id` to the published result. The response can contain a reference to the risk package rather than the full package inline. Use **Overview** for the readable result and the [risk package contract](https://docs.amlok.io/api-reference/risk-package.md) for programmatic retrieval.

Copy or download the JSON to compare the fields with [Data Lookup](https://docs.amlok.io/console/data-lookup.md). For the original HTTP status and timing, open the corresponding request log. An accepted asynchronous request is not yet a completed assessment; a completed assessment is not necessarily a within-policy recommendation.

## Documents

Use this tab to find the files associated with this origination. The table includes **File**, **Type**, **Size**, **Status** and **Added (UTC)**. Search for a file or identifier and select its row to inspect the available metadata.

![File details opened from the Documents tab, showing document and borrower identifiers, available status, record version and Download unavailable.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/origination-documents.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=7365bbbe69ba6cf9113fd7388248d29f)

A file record opened from Documents shows its identity, borrower association and available metadata. This example has no downloadable original.

Check the file's identity and status before relying on it. A dash means metadata is not supplied in that view. A file being listed does not mean every verification check passed or every required document is present.

In the file details, **Download original file** is available when an authorized download is provided. **Download unavailable** means there is no usable download for that record at that time. This is a read-only evidence view; submit or associate additional documents through your integration. See [documents and evidence](https://docs.amlok.io/console/evidence.md) for the wider evidence workflow.

## Integrations

Use this tab to identify the borrower connections associated with the origination, such as banking, payments, commerce or accounting sources. These are case-linked connections, not the catalog of providers enabled in your Integrations Hub.

![Origination Integrations tab listing five synthetic connections and their connected statuses.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/origination-integrations.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=bd61f50706da2f8b8b938c8cff5c36fa)

The Integrations tab shows the connections linked to the underwriting run. Demo sources are synthetic.

The table shows **Integration**, **Provider**, **Status**, **Frequency** and **Last sync**, where recorded. Select a row for its readable details and available source information. Owners and Developers can also inspect captured technical payloads when present.

Check connection status and the available sync timestamps when a result has incomplete or stale evidence. A **Connected** status describes the connection; it does not guarantee that all expected data was retrieved. Missing frequency or sync information is not proof of a failed or successful refresh. Compare the connection with the risk package's coverage and [supporting evidence](https://docs.amlok.io/console/evidence.md).

## Interpret processing and recommendation separately

| What you see | What it tells you |
| - | - |
| **Completed** | Processing produced a result. It does not mean your institution approved the borrower. |
| **Requires action** | Processing needs attention or additional input. Inspect the specific reason and missing evidence. |
| **Failed** | Processing could not complete. Inspect its error and related request records before retrying. |
| **Within policy** | The assessed inputs meet the evaluated policy conditions, subject to the package's coverage and limitations. |
| **Outside policy** | The package identifies policy conditions the assessed inputs do not meet. |
| **Review required** | A person should review the evidence or unresolved conditions. |

The risk package is decision support. Your institution owns the final lending decision. To investigate a case, compare Overview with the captured inputs, then check its documents, connections and request logs. Opening the drawer does not edit the application or rerun underwriting; submit corrections through the documented API workflow.

Continue with [underwriting dimensions](https://docs.amlok.io/api-reference/underwriting-dimensions.md) or follow an enrolled deal in [Portfolio](https://docs.amlok.io/console/portfolio.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.