Denied Party Screening

This API operation is used to submit shipper and/or consignee address information for denied party screening and receive a compliance status indicating whether the address is approved, potentially matched, or matched to a restricted entity. The API does not approve or reject shipments; instead, it provides actionable compliance insights that clients can use to determine next steps.

SecuritybearerAuth
Request
Request Body schema: application/json
required
Array of objects (ScreeningAddress)

List of addresses to be screened. It includes a consignee and/or shipper.

Responses
200

The requested screening report has been retrived successfully.

400

Invalid request.

401

The request could not be authorized.

500

The request could not be completed due to an internal error.

post/api/v1/deniedPartyScreening
Request samples
application/json
{
  • "addresses": [
    ]
}
Response samples
application/json
{
  • "addresses": [
    ]
}