Home
AcuView Quickstart Guide
This guide gives you a brief walkthrough of the AcuView platform and explains how lenders use it to verify borrowers, review loan activity, and interpret borrower health insights. It provides a high-level understanding of AcuView’s features, verification scenarios, and underwriting flow, preparing users for the detailed screen-by-screen guidance in later sections.
Introduction
AcuView is a real-time borrower intelligence platform designed to help lenders evaluate credit risk, verify borrower information, and make safe and informed decisions. The platform combines live borrower activity data, identity and banking verification, and loan-level analysis into a single, unified interface that lenders can use during loan origination and decisioning.
Making API Requests
All AcuView API requests must be made over HTTPS and use JSON request and response bodies. Requests that require authentication must include the Authorization: Bearer <token> header. When the token expires or is missing, the API returns an unauthorized response, and the client must re-authenticate before retrying the request.

AcuView Quickstart Guide
This guide gives you a brief walkthrough of the AcuView platform and explains how lenders use it to verify borrowers, review loan activity, and interpret borrower health insights. It provides a high-level understanding of AcuView’s features, verification scenarios, and underwriting flow, preparing users for the detailed screen-by-screen guidance in later sections.
- Introduction
  AcuView is a real-time borrower intelligence platform designed to help lenders evaluate credit risk, verify borrower information, and make safe and informed decisions. The platform combines live borrower activity data, identity and banking verification, and loan-level analysis into a single, unified interface that lenders can use during loan origination and decisioning.
  - Quickstart Setup
    To begin using AcuView, your integration must be able to make HTTPS requests and send and receive JSON payloads with the Content-Type: application/jsonheader. For core functionality, AcuView also uses a custom header named X-Timezone, which must be set to a valid IANA time zone identifier such as America/Los_Angeles. This time zone header allows AcuView to interpret and present time-sensitive activity, history, and period-based analytics consistently across regions.
  - Create Your First Item
    In AcuView, the first object you typically create is a loan record. Creating a loan record allows AcuView to evaluate borrower data, detect related activity across the network, and return verification and recency insights.
  - How It Works
    AcuView integrations follow a straightforward sequence. First, your application authenticates and establishes a session using POST /api/Authentication/login. The returned token is used to authorize all subsequent API calls.
  - Making API Requests
    All AcuView API requests must be made over HTTPS and use JSON request and response bodies. Requests that require authentication must include the Authorization: Bearer <token> header. When the token expires or is missing, the API returns an unauthorized response, and the client must re-authenticate before retrying the request.
  - Next Steps
    After completing the Quickstart, you can extend your integration to cover additional AcuView capabilities. You can retrieve loan history using GET /api/LoanRecord/loan-history, analyze borrower activity across standard time periods using GET /api/v1/LoanRecord/record-period, and assess borrower risk using GET /api/v1/payments/AssessRisk.
- Features of AcuView
  AcuView provides lenders with a real-time, unified view of borrower activity, helping you verify applicants, understand risk signals, and gain clearer visibility into borrower behavior. The platform brings key borrower intelligence into one place by combining application history, borrower health scoring, recency analytics, and bank verification tools.
- Advantages of AcuView
  AcuView provides lenders with a unified, intelligence-driven platform designed to simplify borrower verification, reduce risk, and accelerate loan review workflows. By combining real-time borrower insights with automated checks and transparent loan history, the platform helps lenders make more informed decisions while improving operational efficiency. The following sections highlight the key advantages AcuView brings to your lending workflow.
- The Borrower Application Action Flow
  AcuView uses a structured status-driven lifecycle to help lenders track borrower applications from the moment they enter the system until the loan is closed. Each status represents a specific stage in the lending process and determines which actions can be taken next. This predictable flow ensures consistent decision-making, improves internal reporting, and aligns all lenders on how borrower applications should progress.
- Understanding the Borrower Verification Scenarios
  AcuView’s verification engine evaluates each borrower through a combination of identity checks, historical analysis, behavioral insights, and fraud indicators. The result of this evaluation is presented as a Verification Scenario, which helps lenders understand how familiar AcuView is with the borrower, whether the information matches known records, and whether there are risks that need further review.

Making API Requests

All AcuView API requests must be made over HTTPS and use JSON request and response bodies. Requests that require authentication must include the Authorization: Bearer <token> header. When the token expires or is missing, the API returns an unauthorized response, and the client must re-authenticate before retrying the request.

For endpoints that process time-based data, the X-Timezone header is required. This ensures that timestamps and activity windows are interpreted consistently. If the time zone value is invalid, the API returns a validation error.

When an error occurs, AcuView returns a structured error response using a ProblemDetails schema. This schema includes a short error summary, HTTP status code, detailed description, and the request path that caused the error. Clients should use both the HTTP status and error body to determine the appropriate next action, such as correcting input data, re-authenticating, or retrying the request.