Making API Requests

All AcuCheck API requests must be made over HTTPS and use JSON request and response bodies. Requests that interact with secured platform capabilities require authentication and must include a valid access token in the request headers.

After successful authentication, the access token must be passed with each request to authorize operations such as customer creation, report requests, report retrieval, and debt-to-income (DTI) evaluation. AcuCheck validates the token on every call to confirm that the request is associated with an active, authenticated session. If the token is missing, expired, or invalid, the request is rejected and must be retried after re-authentication.

AcuCheck enforces permission checks in addition to authentication. Even when a request is authenticated, the platform evaluates whether the authenticated identity has the required permissions to perform the requested action. Requests that exceed the permitted scope are rejected to ensure controlled access to customer financial data and platform configuration.

All API responses follow a structured format. When a request is processed successfully, AcuCheck returns the requested resource or outcome data. When an error occurs, the platform returns a structured error response that includes status information and descriptive details. These responses allow client applications to determine whether corrective action is required, such as adjusting request data, validating permissions, or re-establishing authentication.

Requests that initiate or retrieve report-related data are tightly coupled to report status. Some operations are valid only when a report is in a specific state. For example, DTI outcomes are available only after a report has reached a completed state. This status-aware behavior ensures that results are based on finalized, consolidated customer data.

By enforcing secure transport, token-based authentication, permission validation, and structured responses, AcuCheck ensures that API interactions remain predictable, auditable, and aligned with the platform’s affordability assessment workflows.