Home
📖 VeraFi API Guide
This guide provides comprehensive details about the VeraFi APIs and related information, which is helpful to automate document verification workflows, perform face and liveness checks, and streamline identity verification processes. VeraFi is a financial services platform by AcuFi that offers intelligent verification through document analysis, facial recognition, and liveness detection, enabling secure onboarding, compliance validation, and seamless integration with financial and lending systems.
VeraFi API Host

📖 VeraFi API Guide
This guide provides comprehensive details about the VeraFi APIs and related information, which is helpful to automate document verification workflows, perform face and liveness checks, and streamline identity verification processes. VeraFi is a financial services platform by AcuFi that offers intelligent verification through document analysis, facial recognition, and liveness detection, enabling secure onboarding, compliance validation, and seamless integration with financial and lending systems.
- Quickstart on VeraFi API
- VeraFi API Endpoints and Webhooks
  The VeraFi Backend API provides RESTful endpoints that cover all authentication, verification, configuration, tenant management, subscription management, and microservice proxy operations. These endpoints support identity verification workflows, document processing, bank statement analysis, OTP services, feature management, and system health monitoring.
- VeraFi API Access
  Access to the VeraFi API is governed through a token-based authentication mechanism. To interact with any protected resource, a client must first authenticate using one of the supported login methods. The API allows users to log in either through traditional password-based authentication or through an OTP-based workflow. In both cases, successful authentication results in the issuance of a session token. This token includes the user’s identity, role assignments, tenant details, and subscription information, and is required for performing operations across most endpoints within the system. Once obtained, the token functions as proof of authorization for subsequent requests.
- VeraFi API Protocols and Headers
  All interactions with the VeraFi Backend API follow a secure and structured communication model designed to ensure consistency, reliability, and protection of sensitive information. The API operates exclusively over HTTPS, requiring all requests and responses to be transmitted through encrypted channels. This ensures that sensitive data such as personal information, verification details, and configuration parameters remain protected during transit. Requests made to the API use standard HTTP verbs and follow RESTful principles, allowing integrations to interact with the system using predictable and well-established patterns..
- VeraFi API Host
- VeraFi API Status and Incidents
  The VeraFi Backend API is built to deliver stable, reliable, and consistent performance across all of its verification, authentication, configuration, and subscription workflows. The platform incorporates built-in mechanisms that allow integrators to verify system availability, monitor service responsiveness, and detect operational issues. At the core of these mechanisms are the root endpoint and the dedicated health-check endpoint, both of which enable quick and automated checks to ensure that the API is running before downstream processes are triggered. These endpoints function as lightweight validation tools, helping developers confirm that the system is accepting requests and responding correctly.
- Storing VeraFi API Data
- VeraFi API Field Formats
- VeraFi OpenAPI Defenition File
- Postman Collection
- Common Error Codes
- Integration Best Practices

VeraFi API Host

The VeraFi Backend API is served through a centralized hosting environment that exposes all endpoints under a versioned URL structure. All API operations are accessed through the base path /api/v1. This ensures that the clients can integrate against a stable and predictable namespace. This versioning approach perhaps allows future enhancements or structural changes to be introduced without affecting existing integrations, giving developers a consistent and reliable foundation for long-term use.

The documented version of the VeraFi backend and its API is Version 2.0.0, with the accompanying documentation also marked as Version 2.0.0. The most recent update recorded for the platform and its API definitions is dated October 13, 2025. This version information is important for developers to reference, as it confirms the set of features, structures, and behaviors supported within the current release. Any future versions of the API will follow the same versioned pathing approach, enabling clients to migrate gradually or continue operating against a specific version as needed.

All requests to the VeraFi API must target the defined host environment configured for the deployment in use. The platform follows a structured, microservices-based architecture, and each operation, whether related to authentication, document processing, verification workflows, subscription management, tenant administration, or logging resolves through the unified /api/v1 namespace. This consolidation allows the API to present a cohesive interface while internally delegating the appropriate tasks to various services within the VeraFi ecosystem.

By relying on a stable versioned host and clearly defined endpoint structure, the VeraFi API provides a predictable integration experience that supports long-term compatibility and minimizes disruption as the platform evolves.