UFLPA Entity List Screening

The problem

Under the Uyghur Forced Labor Prevention Act (UFLPA), goods produced by an entity on the UFLPA Entity List are presumed to be made with forced labor and barred from U.S. entry unless the importer rebuts that presumption. Separately, the federal Consolidated Screening List covers denied parties across Commerce, State and Treasury. The two official lists are published separately — one by DHS, one by trade.gov — and either can change after your last check, so every new supplier needs both, and every existing one needs re-checking.

Who it's for

Import-compliance and sourcing teams, customs brokers, and logistics or trade software builders who need to check a supplier or manufacturer against the UFLPA Entity List and denied-party lists before goods move.

Use cases

• Pre-shipment screening of a new supplier or manufacturer before placing a purchase order
• Batch screening a supplier list during onboarding or a periodic compliance review
• Embedding automated risk screening into a customs brokerage or logistics platform

What it does

Send a supplier or manufacturer name and get back a UFLPA Entity List match and a Consolidated Screening List (denied-party) match, plus a deterministic overall exposure rating (none / low / elevated / high). A batch endpoint screens up to 50 suppliers or parties in one call, returning each party's matches and coverage counts (the overall rating is computed for /screen/shipment), and a standalone endpoint offers a direct UFLPA name search. It screens organizations: records the sources classify as individuals are withheld, and the coverage field on a shipment screen says so. An HTS number and country of origin are optional and echoed back for your own reference; this API never derives an HTS number of its own and does not use one to screen anything.

Why Aervik's implementation is different

Exposure scoring is a fixed, deterministic calculation over each source's status — never an AI judgment call — so the same inputs always produce the same risk rating. Every response tells "checked and clear" apart from "not checked": a source that could not be read this time answers status error, and exposure_summary.incomplete_coverage is true whenever any part of the screen is missing, including a result page the source cut short. Both sources are live: there is no placeholder section, and nothing here is labeled "coming soon". And every tariff-line-shaped string that leaves the service is reduced to the 6-digit international HS subheading — this API will fail a request rather than hand back a tariff line it derived, because classification is a licensed customs broker's job, not ours.

Example

Request

POST /screen/shipment
{
  "hts": "7317.00",
  "country_of_origin": "China",
  "supplier_name": "Example Textile Manufacturing Co., Ltd."
}

Response

Captured live 2026-09-15 from the request above, abridged: each source also carries a name, url and note, and the narrative and disclaimer are omitted. Values verbatim.

{
  "input": {
    "hts": "7317.00",
    "country_of_origin": "China",
    "supplier_name": "Example Textile Manufacturing Co., Ltd."
  },
  "coverage": "Entity records only. Records the source classifies as individuals, and records whose name or list suggests an individual, are excluded from this service. Screen individuals at the source directly.",
  "uflpa": {
    "status": "no_match",
    "matches": [],
    "source": {
      "basis": "live",
      "as_of": "2026-07-31"
    }
  },
  "csl": {
    "status": "no_match",
    "matches": [],
    "source": {
      "basis": "live",
      "as_of": null
    },
    "result_page_truncated": false,
    "total_upstream_results": 0,
    "records_below_match_threshold": 0
  },
  "exposure_summary": {
    "overall_risk": "none",
    "reasons": [
      "No UFLPA or Consolidated Screening List hits found for the supplied party names."
    ],
    "incomplete_coverage": false
  }
}

More requests

Screen several parties at once

POST /screen/parties
{ "parties": [ { "name": "Example Supplier Co., Ltd.", "role": "supplier" }, { "name": "Example Manufacturer Ltd.", "role": "manufacturer" } ] }

Search the UFLPA Entity List by name

GET /uflpa/entities?q=Xinjiang

Key features

• One call covers both UFLPA Entity List and Consolidated Screening List (denied-party) exposure
• Deterministic overall exposure rating — none, low, elevated, or high
• Standalone UFLPA Entity List name-search endpoint
• Batch endpoint for supplier/party screening, up to 50 per call
• A source manifest in each screening section: the source, how it was read, and its own date where it publishes one (null where it does not)
• No classification, by design: any HTS number you send is echoed, never derived, and every tariff reference returned is capped at 6 digits

Pricing

A free tier with 30 API requests a month to build against, then monthly plans from $29 with a set number of requests included. The $29 and $99 plans are hard-capped — calls stop at the limit rather than billing you; only the top plan (10,000 requests) runs on a soft limit, with overage at $0.15 per additional request. Batching is cheap: one call screening up to 50 parties counts as a single request.

See exact current pricing tiers on RapidAPI →