plaid

Update individual watchlist screening

Changed on

Update a specific individual watchlist screening. This endpoint can be used to add additional customer information, correct outdated information, add a reference id, assign the individual to a reviewer, and update which program it is associated with. Please note that you may not update search_terms and status at the same time since editing search_terms may trigger an automatic status change.

post/watchlist_screening/individual/update

Request

  • Base URL
    https://production.plaid.com
  • URL
    https://production.plaid.com/watchlist_screening/individual/update
  • Auth
    API key in header PLAID-CLIENT-ID and API key in header PLAID-SECRET and API key in header Plaid-Version

Request body

watchlist_screening_idstring required

ID of the associated screening.

assigneestring

ID of the associated user. To retrieve the email address or other details of the person corresponding to this ID, use /dashboard_user/get.

status'rejected' | 'pending_review' | 'cleared'

A status enum indicating whether a screening is still pending review, has been rejected, or has been cleared.

client_user_idstring

A unique ID that identifies the end user in your system. Either a user_id or the client_user_id must be provided. This ID can also be used to associate user-specific data from other Plaid products. Financial Account Matching requires this field and the /link/token/create client_user_id to be consistent. Personally identifiable information, such as an email address or phone number, should not be used in the client_user_id.

client_idstring

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.

secretstring

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.

reset_fieldsWatchlistScreeningIndividualUpdateRequestResettableField[] nullable

A list of fields to reset back to null

Example request

{
  "watchlist_screening_id": "scr_52xR9LKo77r1Np",
  "search_terms": {
    "watchlist_program_id": "prg_2eRPsDnL66rZ7H",
    "legal_name": "Aleksey Potemkin",
    "date_of_birth": "1990-05-29",
    "document_number": "C31195855",
    "country": "US"
  },
  "assignee": "54350110fedcbaf01234ffee",
  "status": "cleared",
  "client_user_id": "your-db-id-3b24110"
}

Response

OK

idstring required

ID of the associated screening.

assigneestring nullable required

ID of the associated user. To retrieve the email address or other details of the person corresponding to this ID, use /dashboard_user/get.

status'rejected' | 'pending_review' | 'cleared' required

A status enum indicating whether a screening is still pending review, has been rejected, or has been cleared.

client_user_idstring nullable required

A unique ID that identifies the end user in your system. Either a user_id or the client_user_id must be provided. This ID can also be used to associate user-specific data from other Plaid products. Financial Account Matching requires this field and the /link/token/create client_user_id to be consistent. Personally identifiable information, such as an email address or phone number, should not be used in the client_user_id.

request_idstring required

A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive.

Example response

{
  "id": "scr_52xR9LKo77r1Np",
  "search_terms": {
    "watchlist_program_id": "prg_2eRPsDnL66rZ7H",
    "legal_name": "Aleksey Potemkin",
    "date_of_birth": "1990-05-29",
    "document_number": "C31195855",
    "country": "US",
    "version": 1
  },
  "assignee": "54350110fedcbaf01234ffee",
  "status": "cleared",
  "client_user_id": "your-db-id-3b24110",
  "audit_trail": {
    "dashboard_user_id": "54350110fedcbaf01234ffee",
    "timestamp": "2020-07-24T03:26:02Z"
  }
}

Changes

  • a1bbca018160Revision changes
    • warning

      added the new retro enum value to the / response property for the response status

  • be701ec93161Revision changes
    • breaking

      the response property's minLength was decreased from 1 to 0 for the response status

    • breaking

      the / response property's minLength was decreased from 2 to 0 for the response status

    • breaking

      the / response property's minLength was decreased from 4 to 0 for the response status

    • breaking

      the / response property's minLength was decreased from 1 to 0 for the response status

    • info

      the request property's minLength was decreased from 1 to 0

    • info

      the / request property's minLength was decreased from 2 to 0

    • info

      the / request property's minLength was decreased from 4 to 0

    • info

      the / request property's minLength was decreased from 1 to 0