This document covers everything you need to know about connecting Velocity to Broki — the difference between the API and the webhook, the complete step-by-step setup process, what being connected actually enables, and how to troubleshoot common issues including files that won't pull through.
Sections Covered
1. API vs. Webhook — Understanding the Difference
2. What Being Connected Actually Enables
3. Step-by-Step Setup — Complete Connection Guide
4. Verifying the Connection Is Approved
5. How Each User Connects Their Own Velocity Account
6. Troubleshooting — Files That Won't Pull Through
7. Troubleshooting — Pulling Files From Another User's Velocity Account
8. Quick Reference — Where Is That Button?
1. API vs. Webhook — Understanding the Difference
Connecting Velocity to Broki involves two separate components that serve different purposes. It is important to understand what each one does before setting them up.
Velocity API | Enables manual file management between Velocity and Broki. Use the API to: pull a specific file into Broki using a loan code, update an existing Broki file with fresh data from Velocity (e.g. after submitting to a lender and wanting the updated information in Broki), and perform mass pulls of multiple files at once. |
Velocity Webhook | Enables automatic file creation in Broki. When a client fills out a Velocity application, the webhook fires and creates the file in Broki's pipeline automatically — no manual action needed. The webhook also fires when you duplicate a file in Velocity, which will also create a new file in Broki. |
Think of it this way: the API is for manual control (pull this specific file, update this file), and the webhook is for automation (create files automatically when applications come in). Both need to be connected for the full integration to work.
2. What Being Connected Actually Enables
Once both the API and webhook are connected and approved, here is what you gain:
With the API connected
Pull any file from Velocity into Broki manually using the loan code — via the + Add File button in the pipeline.
Click the Update button on any existing Broki file to pull the latest data from Velocity — useful after submitting to a lender.
Perform mass pulls to refresh multiple files at once using the pipeline mass actions.
With the webhook connected
Every new client application submitted through Velocity automatically creates a file in your Broki pipeline — no manual import needed.
Duplicating a file in Velocity also automatically creates a corresponding file in Broki.
⚠ Velocity only allows one API connection at a time. If you are currently connected to another platform (e.g. a different CRM), you must deactivate that connection before connecting to Broki. You cannot run two API connections simultaneously.
3. Step-by-Step Setup — Complete Connection Guide
Follow these steps in order. The process moves between Velocity and Broki several times — read each step carefully before acting.
PART A — Set up the API in Velocity
1 | Go to Velocity Settings Log into Velocity and navigate to your Settings tab. |
2 | Find the Velocity API section Look for the section labeled Velocity API within your settings. |
3 | Check the button state If the blue button says Manage API Keys — you already have an active API connection to another platform. You must deactivate the existing one first before you can connect to Broki. If the blue button says Request API Key — you have no active connection and can proceed directly to Step 5. |
⚠ If you are currently connected to another CRM or platform via the Velocity API, connecting to Broki will replace that connection. Velocity only allows one API integration at a time. Make sure you are ready to switch before deactivating.
4 | Deactivate the existing API (if needed) Click Manage API Keys and deactivate the current active key. Once deactivated, the button will change to Request API Key. |
5 | Request a new API key Click Request API Key. You will be asked to enter a domain. Enter exactly: preview.broki.ca — no typos, no extra characters. This is the most common setup error. If you are unsure, look at the URL in your browser when logged into Broki — the domain is preview.broki.ca. |
⚠ Entering the wrong domain is the number one cause of connection failures. Double-check the spelling before submitting: preview.broki.ca — all lowercase, no www, no trailing slash.
6 | Copy the pending API key After requesting, click Manage API Keys again. Find the key with a status of Pending Approval — this is the one you just requested. Check the creation date and time to confirm it is the most recent one. Copy this key. |
PART B — Connect the API in Broki
7 | Go to Broki Settings Log into Broki. Go to Settings → scroll down to Integrations & Connections → click Origination Platforms. |
8 | Find the Velocity integration Locate the Velocity section. If you have an existing integration already connected, click Manage and remove the old one before proceeding. |
9 | Paste the API key into both fields You will see two fields: Velocity API Key and Confirm API Key. Paste the key you copied from Velocity into both fields — they must match exactly. |
10 | Click Configure Integration Click the purple Configure Integration button (bottom right). The API connection is now established. A webhook URL is automatically generated and displayed at the top of the integration panel. Copy this webhook URL — you will need it in the next step. |
PART C — Connect the Webhook in Velocity
11 | Go back to Velocity Settings Return to your Velocity settings page. |
12 | Find the Velocity Webhooks section Locate the Velocity Webhooks section (separate from the API section). |
13 | Click Request Webhook Click the Request Webhook button. |
14 | Paste the webhook URL Paste the webhook URL you copied from Broki into the webhook input field. |
15 | Select both trigger events Check both boxes: Deal Created and All Deal Status Updates. Both must be selected for the full integration to work correctly. |
16 | Click Request Webhook Click the Request Webhook button to submit. You should see a confirmation message that says Velocity Webhook Request Sent. |
✓ Setup complete. Both the API and webhook have been submitted. However, both need to be approved before the connection is fully active — see Section 4.
4. Verifying the Connection Is Approved
After submitting both the API key and the webhook, they need to be approved before they will work. This typically takes a couple of hours.
How to check API key approval status
Go to Velocity Settings → Velocity API → Manage API Keys.
Find your key and check the status. It will show Pending Approval until it is ready.
Once approved, the status will update. Files can only be pulled and the webhook will only fire once the status is Approved.
How to check webhook approval status
Go to Velocity Settings → Velocity Webhooks.
Click the gear icon next to your webhook.
The approval status is visible here.
⚠ Do not attempt to pull files or expect applications to auto-create in Broki until both the API key and webhook show as Approved in Velocity. Attempting to use them before approval will not work.
5. How Each User Connects Their Own Velocity Account
In Broki, each individual user connects their own personal Velocity account. The connection is not shared across all team members — it is per-user.
Every broker or team member who uses Velocity needs to complete the setup process above using their own Velocity credentials and their own API key.
When a user pulls a file from Velocity in Broki, it uses their personal connected Velocity account to fetch the data.
If a user has not connected their Velocity account, they will not be able to pull files or trigger updates from Velocity.
This is typically not an issue in day-to-day use because most files are created automatically via the webhook when clients submit applications. The per-user API connection primarily matters when importing older files manually — see Section 7.
6. Troubleshooting — Files That Won't Pull Through
If you are trying to manually pull a file using a loan code and it is not working, here are the most common reasons:
API not properly connected | The Velocity API key in Broki is either not entered correctly, not yet approved, or has been deactivated in Velocity. Re-check the connection status in both Velocity (Manage API Keys) and Broki (Settings → Connections → Origination Platforms → Velocity → Manage). |
Client consent not given | Velocity restricts data sharing for files where the client did not go through the online application process and consent to data being shared with third-party platforms. If you filled out the application on the client's behalf and they never went through the online application themselves, the consent may not have been recorded — which can prevent the file from being pulled into Broki. |
File not yet validated in Velocity | A file that has not yet been submitted to the lender and validated in Velocity may not be eligible to be pulled. Once the file has been submitted and validated in Velocity, pulling it into Broki typically works. This is a Velocity-side restriction. |
Pulling someone else's file | If you are trying to pull a file that belongs to another broker's Velocity account and that broker's account is not the one connected in Broki, the pull will fail. See Section 7 for details. |
7. Troubleshooting — Pulling Files From Another User's Velocity Account
This is a common point of confusion for teams. The key rule to understand is:
A file can only be pulled from Velocity by the user whose Velocity account it belongs to.
This is a Velocity security rule — not a Broki limitation.
What this means in practice
If a broker on your team has their own Velocity account and you (as an admin or another user) try to pull their file using your connected Velocity account, it will not work.
The first pull of any file must be done by the user whose Velocity account the file lives in.
Once a file has been pulled into Broki for the first time by the correct user, any team member can click Update on that file to refresh it — because it is already synced.
How to handle this for importing old files
Have each broker log into Broki themselves and pull their own files using their own connected Velocity account.
Alternatively, have the broker use the mass pull feature in the pipeline to import all their files in one action.
Once the initial pull is done by the correct user, the file is in Broki and any team member can update it going forward.
In normal day-to-day use, this issue almost never comes up — because the webhook creates files automatically when clients fill out applications, so manual pulling is rarely needed except for importing historical files. If you are migrating old files into Broki, make sure each broker does their own initial import.
8. Quick Reference — Where Is That Button?
Button / Feature | Location | What it does |
Velocity API section | Velocity → Settings | Where you request, manage, and deactivate Velocity API keys |
Manage API Keys | Velocity → Settings → Velocity API | Shows all API keys and their approval status — use to copy the pending key or deactivate an old one |
Request API Key | Velocity → Settings → Velocity API (when no active key exists) | Generates a new API key for a specific domain (enter preview.broki.ca) |
Deactivate (existing key) | Velocity → Settings → Velocity API → Manage | Deactivates the current API key so a new one can be requested for Broki |
Velocity Webhooks section | Velocity → Settings | Where you request and manage webhooks |
Request Webhook | Velocity → Settings → Velocity Webhooks | Submit a new webhook URL — paste the URL generated from Broki here |
Deal Created + All Deal Status Updates | Velocity webhook setup — trigger selection | Both must be checked for the full webhook integration to function |
Gear icon (webhook) | Velocity → Settings → Velocity Webhooks → next to webhook entry | Shows the approval status of the webhook |
Integrations & Connections | Broki → Settings → scroll down | Access all platform integrations including Velocity and FINMO |
Origination Platforms | Broki → Settings → Integrations & Connections | Find Velocity and FINMO integration management here |
Velocity → Manage | Broki → Settings → Integrations → Origination Platforms → Velocity | Open the Velocity API connection panel in Broki |
Velocity API Key field | Broki → Velocity integration panel | Paste the Velocity API key here |
Confirm API Key field | Broki → Velocity integration panel | Paste the same Velocity API key here to confirm |
Configure Integration (purple button) | Broki → Velocity integration panel — bottom right | Saves the API key and generates the webhook URL |
Webhook URL | Broki → Velocity integration panel — top, after configuring | The URL to paste into Velocity's webhook section |
+ Add File (pipeline) | Broki pipeline — second toolbar row | Manually pull a specific Velocity file using its loan code (requires API to be connected and approved) |
Update button (on file) | On any existing Broki file | Pulls fresh data from Velocity for that file (requires API connected) |