Obtain a MeridianLink LoansPQ Vendor Software ID and credentials by completing the LoansPQ vendor integration onboarding process
Review the Loan web service WSDL/documentation to identify the createLoan and updateLoan method signatures for your institution's configuration
Construct a SOAP or REST-style call to the Loan web service endpoint to create a new application record, supplying borrower demographics, requested product, and loan amount
Capture the returned loan application ID and use it for subsequent getLoan calls to retrieve application status and decision data
For decisioning integrations, use the MeridianLink Credit API to attach a credit report pull event to the application and retrieve the resulting score and report data
Test all methods in the LoansPQ sandbox environment before submitting to production; the MeridianLink third-party integration documentation provides test data sets and expected responses
Known gotchas
LoansPQ uses web service-based integration; the specific endpoint URL and transport protocol (SOAP vs REST) depend on the institution's configuration — confirm with the lender's IT team before building
MeridianLink's 200+ third-party integrations mean field mappings can vary by institution; always request the institution-specific field mapping guide rather than relying solely on the standard API spec
Vendor access requires a formal onboarding session and a Partner/Software Vendor ID; self-provisioning is not available
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp