Sign in to SALT

QuoteRUSH integration guide

QuoteRUSH is a comparative rater integration covering personal lines (home and auto). Connect with your four QuoteRUSH API credentials, then send a completed Submission manually — home and auto can go together as a single bundled lead. Sending locks the Insured and line-of-business data so the lead in QuoteRUSH matches what you sent.

Updated Jun 16, 2026 • For agency admin

In short: Connect QuoteRUSH with your four API credentials (Web ID, Web Password, Endpoint Key, Agency), then manually send a completed Submission. Home and auto can be sent together as one lead. Once sent, the Insured and that line’s data lock.

What QuoteRUSH covers

QuoteRUSH is a comparative rater for personal lines — home and auto. When you send a Submission, SALT pushes:

  • Insured contact and profile information
  • Drivers and vehicles (for auto)
  • Property and risk details (for home)
  • Coverage preferences and requested limits
  • Prior policy details (where captured)

QuoteRUSH imports the lead and makes it available for quoting in your QuoteRUSH account.

Connect QuoteRUSH

QuoteRUSH uses four API credentials, all found in QuoteRUSH under Agency Settings → API Information (open Agency Settings):

  • Web ID — your agency’s WebID (e.g. CAKO257872947).
  • Web Password — the WebID Password QuoteRUSH issued for your agency. Used to authenticate every lead push.
  • Endpoint Key — the API endpoint key for your agency.
  • Agency — the agency identifier QuoteRUSH provides (usually a GUID matching the Endpoint Key). This is not your agency’s display name.
  1. 1

    Open Integrations on your account.

  2. 2

    Find QuoteRUSH and click connect.

  3. 3

    Enter all four credentials from QuoteRUSH’s API Information panel.

  4. 4

    Save — SALT validates the credentials against QuoteRUSH before activating. If the Web ID or Web Password is wrong, activation is rejected with an error so you can correct it.

  5. 5

    Once connected, QuoteRUSH appears as your active rater and is ready to receive sends.

If validation fails, double-check the Web ID and Web Password first — those are the two values QuoteRUSH authenticates on. The Endpoint Key and Agency must also be present, but a rejection usually points to the Web ID/Password pair.

Sending a Submission to QuoteRUSH

QuoteRUSH sends are manual — you send a completed Submission when you’re ready, rather than it firing automatically on completion. From the Submission you choose what to send:

  • Home only or auto only — sends that single line.
  • Home & auto together — sends both as a single bundled lead, so one insured arrives as one lead in QuoteRUSH.

QuoteRUSH does not deduplicate leads. If you send home now and auto later (instead of bundling them), QuoteRUSH creates two separate leads for the same insured. When both lines are ready, send them together to keep them on one lead.

Sending locks the data

Once a Submission is sent to QuoteRUSH, its Insured and the sent line’s data are no longer editable in SALT. This keeps the lead in QuoteRUSH consistent with what SALT sent. Make sure the Submission is complete and correct before sending.

Sync status

After a send, SALT records the result on the Submission so you can see where each line stands:

  • Synced — QuoteRUSH accepted the lead.
  • Failed — QuoteRUSH rejected the send, or returned an error. Check the error detail and re-send after fixing the underlying data.
  • Not Synced — the line hasn’t been sent yet.

Each line of business reports its own status, so on a bundled home + auto Submission you can see both independently.

Why some fields aren’t sent

Not every SALT field maps to QuoteRUSH — the two systems have different data shapes. SALT sends the fields QuoteRUSH’s import accepts; anything without a corresponding QuoteRUSH field stays in SALT for export and follow-up.

For the exact, current list of every field SALT sends to QuoteRUSH — and the values QuoteRUSH accepts — see the QuoteRUSH field reference. If you need a field sent that isn’t currently mapped, contact support to discuss extending the field map.

Troubleshooting failed sends

If a QuoteRUSH send fails:

  1. Check the credentials. Expired or changed API credentials cause rejections. Re-enter them from QuoteRUSH’s API Information panel.
  2. Check the Submission for missing required fields. QuoteRUSH requires certain data per line (insured address and phone, vehicle details for auto, property address for home). Missing required fields cause rejection.
  3. Check the sync status on the Submission. A line marked Failed carries the reason QuoteRUSH returned.
  4. Re-send after correcting. Because a failed line isn’t locked, you can fix the data and send again.

Common questions

Where do I find my QuoteRUSH credentials? In QuoteRUSH under Agency Settings → API Information. You need all four: Web ID, Web Password, Endpoint Key, and Agency.

Why did QuoteRUSH create two leads for the same insured? The home and auto lines were sent separately. QuoteRUSH doesn’t deduplicate, so each send becomes its own lead. Send both lines together to keep them on one lead.

Can I edit a Submission after sending it to QuoteRUSH? No. Sending locks the Insured and the sent line’s data so SALT stays consistent with the lead in QuoteRUSH. Confirm everything before sending.

Can I run QuoteRUSH and another rater on the same Submission? QuoteRUSH is the team’s active comparative rater when selected. For how multiple raters coexist on your account, see Which questions are sent to which integration.

Does QuoteRUSH sync count toward Data Credits? No. Comparative raters don’t consume Data Credits.

Which questions actually get sent to QuoteRUSH? See the QuoteRUSH field reference for the live, introspected field map.