Sign in to SALT

Setting per-vendor data thresholds

A per-vendor monthly threshold caps how many lookups SALT runs against a specific data provider per month. Useful for cost control on a vendor you don't want to over-consume. When hit, that vendor pauses regardless of your overall credit balance.

Updated Apr 29, 2026 • For agency admin

In short: Set “Manage Monthly Limit” on each integration to cap that vendor’s monthly usage. When the cap is hit, that vendor pauses for the rest of the month even if your overall credit balance is healthy.

What the threshold does

Without a threshold, an integration runs as many lookups as the Data Credit balance allows. For agencies that want hard caps per vendor — to prevent runaway cost on one provider — the per-vendor monthly threshold is the lever.

When the threshold is hit:

  • The vendor is paused for the rest of the calendar month
  • The integration shows a “threshold” status on Submissions where it would have fired
  • New Submissions don’t trigger that vendor (others continue normally)
  • Your overall credit balance is unaffected by the pause

Why pulls might stop while credits remain

If you’re seeing pulls fail for one vendor but not others, and your balance is healthy, check that vendor’s monthly threshold. Most likely it’s been hit.

To verify:

  1. Open the integration in question
  2. Look at the monthly usage vs threshold display
  3. If at the cap, that’s the explanation

Set or change a threshold

  1. 1

    Open the integration on your account.

  2. 2

    Find the option to manage monthly limit (typically labeled “Manage Monthly Limit” in the UI).

  3. 3

    Set the credit cap for the vendor for the current month.

  4. 4

    Save.

The threshold can be raised or lowered any time. Raising mid-month immediately resumes the vendor (assuming overall balance also allows). Lowering takes effect on the next pull — past pulls already counted against the new lower limit.

Resetting at month boundaries

Thresholds reset on the calendar month boundary. On the 1st of each month:

  • Per-vendor counters reset to zero
  • Paused vendors resume normally
  • Threshold settings carry over from previous month (no need to re-configure)

Strategic threshold setting

A few patterns:

  • Conservative cap on the most expensive vendor (typically MeasureOne for dec pages). Caps protect against unexpected spikes.
  • Higher cap on lighter vendors (Estated, Fenris property data) where per-pull cost is low and volume is fine.
  • Zero cap = effectively disabled — useful for temporarily turning off a vendor without disconnecting.

What “threshold met” looks like on a Submission

When a pull would have fired but the vendor is at threshold:

  • The Submission shows the integration as paused for that pull
  • The data isn’t fetched
  • No credits are consumed for the would-be pull
  • The pull doesn’t auto-retry next month — it’s permanently skipped for that Submission

If you raise the threshold or wait for the month to reset, you can manually re-trigger pulls on past Submissions where supported.

Common questions

Where are thresholds set? Thresholds are configured at the agency level for each integration that supports them.

Will I get a notification when a threshold is hit? Threshold-hit alerts surface in the integration’s status. Some configurations also email or post notifications.

Does an exceeded threshold consume credits? No — a paused pull consumes nothing. Credits are only debited when a lookup actually runs.

My threshold is generous but pulls still aren’t firing. Check overall balance, integration status (disabled or needs-reauth), Form toggle, and recent error logs. The threshold is only one of several gates.