Skip to main content
DELETE
Delete the screening policy for a vendor

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

environmentId
string
required

ID of the environment

Required string length: 36
Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Example:

"95b11417-f18f-457f-8804-68e361f9164f"

providerType
enum<string>
required

Screening vendor the policy belongs to Screening vendor a policy belongs to. Deliberately not ProviderEnum, which is a 44-value auth/social/onramp list of which only these two are screening vendors. The Dynamic sanctions provider is absent because the sanctions floor is generated from code and is not configurable.

Available options:
trmWalletScreening,
chainalysisAddressScreening
scope
enum<string>
required

Which screening moment this policy governs. An environment holds one policy per vendor per scope, authored independently. Which screening moment a policy governs. An environment holds one policy per vendor per scope, authored independently — a customer may alert at sign-in and block on transactions, or skip the paid vendor call at one and not the other. Two values, not three: an "applies to both" policy would make the overlap with a single-scope row unrepresentable as a unique constraint.

Available options:
SIGN_IN,
TRANSACTION

Response

The screening policy was deleted

Last modified on August 30, 2026