Connect Velocity to BrokerDam

1. Request your API key in Velocity

   Sign in to Velocity and open its settings area, where API access is managed. Request an API key for your account. The request goes to Newton for approval — you don't get the key on the spot. When it's approved, Newton emails the key to you.

   Treat that email like a password. The key gives BrokerDam read access to your Velocity book, so don't forward it or paste it into a shared document.

2. Open the Velocity integration in BrokerDam

   In BrokerDam, go to Settings → Integrations → Velocity. This is the single place the connection is configured; you don't need to touch anything on the deal side first.

3. Paste the key and connect

   Paste the key from Newton's email into the API key field and confirm the connection. BrokerDam validates the key against Velocity — if it's rejected, the most common causes are a partially copied key (watch for trailing spaces) or a key that hasn't finished being approved on Newton's side yet.

4. Run your first sync

   Once connected, start a sync to pull your data across. BrokerDam brings in your deals along with their borrowers and co-borrowers, so applicants arrive attached to the right file rather than as a loose contact list.

   The first sync is the largest one. Later syncs only have to reconcile what's changed, so they finish faster.

5. Know what the API can and can't reach

   The Velocity API exposes your recent book — the deals you're actively working and those you've closed recently. Older history that sits outside that window doesn't come across the API. To get it into BrokerDam, export it from Velocity as a file and bring it in through the file import instead.

6. Re-sync when you need fresh data

   Syncing is on demand: you decide when it runs, by starting it yourself from the Velocity integration screen. Nothing runs on a hidden schedule in the background, so what you see in BrokerDam reflects your last sync.

   A good habit is to sync at the start of the day, and again after a batch of updates in Velocity, so your pipeline view matches your submissions.

One direction only. The sync reads from Velocity into BrokerDam. Nothing BrokerDam holds is written back to Velocity, so you can work in BrokerDam without worrying about overwriting anything in your lender-facing system of record.

If a sync looks incomplete. Check whether the missing deals fall outside the API's recent-book window — that's usually the answer, and the fix is a file import rather than another sync.