# Sweep thresholds

A **sweep threshold** is the minimum amount of an asset that triggers a sweep. Thresholds are configured per domain for each (ticker, ledger) pair in the Ripple Custody catalog.

## List sweep threshold configurations for a domain

 - [GET /v1/domains/{domainId}/sweep-thresholds](https://docs.ripple.com/products/custody/reference/api/openapi/sweep-thresholds/getsweepthresholds.md): Returns min sweep thresholds for every asset supported by Custody, optionally filtered by ledger. The list is composed from the live Custody ticker/ledger catalog: assets without an explicitly configured threshold default to "0" (immediate sweep) and carry no id/createdAt/updatedAt.

## Bulk update sweep threshold configurations

 - [PUT /v1/domains/{domainId}/sweep-thresholds](https://docs.ripple.com/products/custody/reference/api/openapi/sweep-thresholds/updatesweepthresholds.md): Upserts multiple sweep thresholds in a single transaction: a threshold row is created on first configuration of an asset and updated thereafter. Each (tickerId, ledgerId) pair must exist in the Custody catalog. All updates are applied atomically (all-or-nothing); if any update fails, the entire request is rolled back.  Optimistic locking: send the version from the corresponding GET row in each update. If any submitted version no longer matches the stored row (or a version is sent for an asset that has since been configured), the whole request is rejected with 409 and nothing is written.