Velocity

Last reviewed: July 2026

Overview

Integuru's Velocity integration provides production-ready HTTP API access to Velocity, the lending and financial operations platform at velocity-beta-app.newton.ca, covering 1 action: get_velocity_crm_aml_enrichment. Full API documentation is available for this action.

No public API. Velocity does not expose a developer API. Teams that need borrower AML enrichment data as part of an automated underwriting or compliance workflow have previously had to retrieve it manually through the platform UI, making it impractical to include in any programmatic pipeline.

The get_velocity_crm_aml_enrichment action takes a Velocity loan code (formatted as VBLUE-123456) and returns structured AML enrichment data for all borrowers associated with that deal. When includeEvidence is true (the default), each returned field is wrapped in a structured object containing value, sourceEndpoint, responsePath, rawLabel, and uiSection, giving compliance systems a full audit trail for every data point.

Fintech engineers and compliance automation teams use this integration to pull borrower AML data into underwriting pipelines, compliance review tools, and risk scoring systems without manual intervention. Browse the full integrations catalogue for other Finance & Investing platform integrations.

---

Use Cases

Integuru's Velocity integration gives your team programmatic access to borrower AML enrichment data scoped to a specific loan deal, with filtering options to target individual borrowers and control the response payload shape.

• AML enrichment retrieval: Call get_velocity_crm_aml_enrichment with a loanCode to return structured AML data for all borrowers on the deal. The response includes the full enrichment payload by default.
• Targeted borrower lookup: Use borrowerName (substring match, case-insensitive), borrowerEmail (exact match, case-insensitive), or borrowerIndex (0-based position in the deal's borrower list) to return data for a single borrower rather than all borrowers on a deal.
• Section and field filtering: Pass a sections array to limit the response to specific top-level data categories, or use dot-path notation in the fields array (e.g. 'riskAssessment.isPep', 'employmentTenure.yearsAt') to retrieve individual fields within a section, reducing payload size in high-frequency compliance pipelines.
• Evidence-stripped responses: Set includeEvidence: false to receive plain field values instead of the default evidence-wrapped objects, useful when you only need the data values and want a lighter response for downstream processing.

---

Setup Notes

Integuru's Velocity integration authenticates against https://velocity-beta-app.newton.ca/. Integuru handles the login session automatically; you configure credentials once during setup and the integration manages re-authentication from that point forward.

Loan code format: The loanCode parameter follows the pattern VBLUE-123456. Pass the full code as it appears in the Velocity platform, including the prefix segment.

Borrower filtering: The borrowerName, borrowerEmail, and borrowerIndex parameters are independent optional filters. Only one should be needed per call; using multiple will narrow results to borrowers matching all supplied criteria simultaneously.

sections vs. fields: The sections parameter selects entire top-level response sections; the fields parameter selects individual fields using dot-path notation and implicitly includes the parent section. Pass an unknown section name and the action returns a 400 error, so confirm valid section names from the full API documentation before using this parameter in production. Omit both parameters to receive the complete response.

includeEvidence default: includeEvidence defaults to true, meaning every returned field arrives as an evidence object with value, sourceEndpoint, responsePath, rawLabel, and uiSection. Set it to false only when the downstream system expects plain values and does not need the audit metadata.