POST /beacon/account_risk/v1/evaluate

Use /beacon/account_risk/v1/evaluate to get risk insights for a linked account.

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
device Object No

Details about the end user's device. When calling /signal/evaluate or /signal/processor/evaluate, this field is optional, but strongly recommended to increase the accuracy of Signal results.

device.ip_address String No

The IP address of the device that initiated the transaction

device.user_agent String No

The user agent of the device that initiated the transaction (e.g. "Mozilla/5.0")

client_id String No

Your Plaid API client_id. The client_id is required and may be provided either in the PLAID-CLIENT-ID header or as part of a request body.

options Object No

An optional object to filter /beacon/account_risk/v1/evaluate results to a subset of the accounts on the linked Item.

options.account_ids[] Array No

An array of account_ids for the specific accounts to evaluate.

evaluate_time String No

The time the event for evaluation has occurred. Populate this field for backfilling data. If you don’t populate this field, we’ll use the timestamp at the time of receipt. Use ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ).

evaluation_reason String No

Description of the reason you want to evaluate risk. ONBOARDING: user links a first bank account as part of the onboarding flow of your platform. NEW_ACCOUNT: user links another bank account or replaces the currently linked bank account on your platform. INFORMATION_CHANGE: user changes their information on your platform, e.g., updating their phone number. DORMANT_USER: you decide to re-evaluate a user that becomes active after a period of inactivity.
OTHER: any other reasons not listed here Possible values: ONBOARDING, NEW_ACCOUNT, INFORMATION_CHANGE, DORMANT_USER, OTHER

Possible values:

  • "OTHER"
  • "DORMANT_USER"
  • "ONBOARDING"
  • "INFORMATION_CHANGE"
  • "NEW_ACCOUNT"
client_evaluation_id String No

Unique identifier of what you are looking to evaluate (account add, information change, etc.) to allow us to tie the activity to the decisions and possible fraud outcome sent via our feedback endpoints. You can use your internal request ID or similar.

access_token String No

The access token associated with the Item data is being requested for.

secret String No

Your Plaid API secret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.

client_user_id String No

A unique ID that identifies the end user in your system. This ID is used to correlate requests by a user with multiple evaluations and/or multiple linked accounts. Personally identifiable information, such as an email address or phone number, should not be used in the client_user_id.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.