Entry details

Request

Body

{
  "name": "RABITA TRUST"
}

Response

A single entryData object, keyed by source list. Only lists holding the name are present, and each key holds an array because one name can appear on a list more than once: several SEC filings, a company against several vessels, or a PEP with one row per office held.

There is no api_usage_id here. The endpoint issues no screening RPC and is not metered, since it is a follow-up to a search you have already been charged for.

Body

{
  "entryData": {
    "ofac_sdn": [
      {
        "name": "RABITA TRUST",
        "uid": "6980",
        "sdn_type": "Entity",
        "programs": "SDGT",
        "aliases": "RABITA TRUST FUND",
        "addresses": "Room 9a, Second Floor, Wahdat Road, Lahore, Pakistan"
      }
    ],
    "un_consolidated": [
      {
        "name": "RABITA TRUST",
        "un_list_type": "Al-Qaida",
        "reference_number": "QDe.005",
        "listed_on": "2001-10-17"
      }
    ]
  }
}

Note that the two records above share only name. Treat each list’s object as its own shape and read the fields you need per list.

Fields by list

The 16 lists this endpoint can return, with how many fields each record carries. Open a list for the full field-by-field breakdown.

One key covers more than one list: sec holds all five SEC streams, and each record names its own with a sec_list field of litigation_releases, administrative_proceedings, trading_suspensions, pause or receiverships. Screening reports these as separate lists, so read sec_list to line an entry record up with the match that led you to it.

Example

curl -X POST https://api.amlscreen.io/api/entry-details \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{ "name": "RABITA TRUST" }'