Home
📖 AcuView API Guide
This guide provides comprehensive details about the AcuView APIs and related information, which is helpful to generate real-time borrower intelligence. AcuView is a financial services platform by AcuFi that delivers instant visibility into borrower activity across the lender network and supports smarter lending decisions through early alerts and account verification.
Common Error Codes

📖 AcuView API Guide
This guide provides comprehensive details about the AcuView APIs and related information, which is helpful to generate real-time borrower intelligence. AcuView is a financial services platform by AcuFi that delivers instant visibility into borrower activity across the lender network and supports smarter lending decisions through early alerts and account verification.
- Quickstart on AcuView API
- AcuView API Endpoints and Webhooks
  The AcuView API is divided into three main categories of endpoints. Authentication endpoints allow users to establish and manage secure sessions using login and identity check operations. Bank Account Verification endpoints validate customer account information against our application’s records to ensure accuracy and reduce errors or misuse. Loan Record Management endpoints provide the ability to create and check new loan applications, search and retrieve loan records, manage the status of loan applications, and view loan history.
- AcuView API Access
  Access to the AcuView API is secured through a token-based authentication mechanism.
- AcuView API Protocols and Headers
  All interactions with the AcuView API are conducted over HTTPS, and only secure TLS connections are supported.
- AcuView API Host
- AcuView API Status and Incidents
  The AcuView API is designed for reliability and high availability.
- Storing AcuView API Data
- AcuView API Field Formats
- AcuView OpenAPI Defenition File
- Postman Collection
- Common Error Codes
- Integration Best Practices

Common Error Codes

Note:

Please contact AcuFi Support if you require more information on specific error codes.

AcuView uses a ProblemDetails JSON schema to provide structured error responses. This allows developers to capture consistent error details across all endpoints.

Error Response Schema

{
  "type": "string",      // URI reference identifying the error type
  "title": "string",     // Short, human-readable summary
  "status": 400,         // HTTP status code
  "detail": "string",    // Detailed error description
  "instance": "string"   // Request path that caused the error
}

Common Errors

Table 1. Common errors and resolution table
HTTP Code	Error Code	Message	Resolution
400	`INVALID_REQUEST`	Invalid request data or parameters	Check payload, query params, or headers. Ensure required fields are correctly formatted.
401	`UNAUTHORIZED`	Authentication required or invalid credentials	Verify that a valid JWT token is provided in the `Authorization` header using the format: `Authorization: Bearer <your_token>`
403	`FORBIDDEN`	Insufficient permissions	Confirm the account has the correct role/permissions. Contact admin if necessary.
404	`NOT_FOUND`	Requested resource not found	Verify resource ID, endpoint path, or query filters.
500	`INTERNAL_ERROR`	Server-side error occurred	Retry after some time. If persistent, contact AcuView support with request details.