Skip to main content

Field Mapping

Field Mapping Tables: World-Check Data File​

Main File​

The table below provides a quick view of the mapping between legacy World-Check Data file fields from the Main File and World-Check On Demand objects. Click the legacy field names for more details.

World-Check Data File Record FieldWorld-Check On Demand Object/FieldNotes/Conditions
UIDrecord.uid
LAST NAMErecord.nameInformation.nameDetails.details.value(role = wcNameRole:LAST_NAME -or-
role = wcNameRole:STRING_NAME) -and-
isDefault = true
FIRST NAMErecord.nameInformation.nameDetails.details.valuerole = wcNameRole:FIRST_NAME-and-
isDefault = true
ALIASESrecord.nameInformation.nameDetails.details.valuerole = wcNameRole:STRING_NAME -and-
relations.value = wcNameType:AKA
LOW QUALITY ALIASESrecord.nameInformation.nameDetails.details.valuerole = wcNameRole:STRING_NAME -and-
relations.value = wcNameType:LQA
ALTERNATIVE SPELLINGrecord.nameInformation.nameDetails.details.valuerole = wcNameRole:STRING_NAME -and-
relations.value = wcNameType:AKA
CATEGORYrecord.recordType.value -or-
record.recordType.recordSubTypes.value -or-
record.categoryInformation.categories.categoryPath		The WCDF CATEGORY values are now in these World-Check On Demand objects.
TITLErecord.nameInformation.nameDetails.details.valuerole = wcNameRole:SINGLE_TITLE -or-
role = wcNameRole:SINGLE_TITLE_AS_IS
SUB-CATEGORYrecord.categoryInformation.categories.categoryPathThese are now part of the wcCat2 concepts in World-Check On Demand.
POSITIONrecord.pepRoleInformation.pepRoleDetails.position.valueIn World-Check On Demand, each PEP Role entry has a position object. There is no default position.
AGErecord.dateInformation.dateDetails.details.valueWorld-Check On Demand does not provide the numeric age but calculates the likely min/max year of birth based on both AGE and AGE DATE (AS OF DATE) and appears as the value where type = wcDateType:CALCULATED_YOB
DOBrecord.dateInformation.dateDetails.details.valuetype = wcDateType:REPORTED_DOB -and-
isDefault = true
DOBSrecord.dateInformation.dateDetails.details.valuetype = wcDateType:REPORTED_DOB -and-
isDefault = false or not present
PLACE OF BIRTHrecord.locationInformation.locationDetails.details.valuetype = wcLocationType:BIRTH_LOCATION -and-
role = wcLocationRole:STRING_LOCATION
DECEASEDrecord.dateInformation.dateDetails.details.valuetype = wcDateType:DECEASED_DATE
PASSPORTSrecord.identificationInformation.identificationDetails.details.valuetype = wcIdentificationType:PASSPORT -with-
role = wcIdentificationRole:VALUE -and-
role = wcIdentificationRole:ISSUING_COUNTRY
SSNrecord.identificationInformation.identificationDetails.details.valueData have been merged with the rest of the ID Numbers in World-Check On Demand and will have a SSN type value based on the country, like wcIdentificationType:US_SSN for the United States.
IDENTIFICATION NUMBERSrecord.identificationInformation.identificationDetails.details.valueFilter by the type of wcIdentificationType concept. The role provide the context.
LOCATIONSrecord.locationInformation.locationDetails.details.valuetype = wcLocationType:UNDETERMINED_LOCATION
The LOCATIONS information has been structured into Country, State/Province, and City in World-Check On Demand.
COUNTRIESrecord.locationInformation.locationDetails.details.valuetype = wcLocationType:CITIZENSHIP_LOCATION -and-
isDefault = true
CITIZENSHIPrecord.locationInformation.locationDetails.details.valuetype = wcLocationType:CITIZENSHIP_LOCATION -and-
isDefault = false or not present
COMPANIESrecord.connectionInformation.connectionDetails.valuetype ≠ wcRecordType:IND -and-
(valueDataType = wcDataType:UID -or-
valueDataType = wcDataType:STRING)
E/Irecord.recordType.value -or-
record.genderInformation.genderDetails.details.value		WCDF's E/I field is used for both record type information (e.g., E) and gender (e.g., M or F)
LINKED TOrecord.connectionInformation.connectionDetails.valuetype = wcRecordType:IND -and-
(valueDataType = wcDataType:UID -or-
valueDataType = wcDataType:STRING)
FURTHER INFORMATIONrecord.furtherInformation.furtherDetails.details.valuerole = wcFurtherInformation:REPORTS with no further information reported are not returned
KEYWORDSrecord.keywordReferenceList.keywordTag.keyword
EXTERNAL SOURCESrecord.sourceReferenceList.sourceRefs.value
UPDATE CATEGORYrecordMeta.changeHistory.updateCategory
ENTEREDrecordMeta.initialPublisheddate
UPDATEDrecordMeta.lastPublishedDate
EDITORN/A
AGE DATE (AS OF DATE)record.dateInformation.dateDetails.details.valuetype = wcDateType:CALCULATED_YOB - this is now provided as a minimum and maximum year of birth
PEP ROLESrecord.pepRoleInformation.pepRoleDetails.role.value
PEP STATUSrecord.pepRoleInformation.status.value
SPECIAL INTEREST CATEGORIESrecord.categoryInformation.categories.categoryPathwcCat1:SPECIAL_INTEREST_CATEGORY and its child categories

Native Character File​

The table below provides a quick view of the mapping between legacy World-Check Data File fields from the Native Character file and World-Check On Demand objects. Click the legacy field names for more details.

World-Check Data (Native Character) File Record FieldWorld-Check On Demand Object/FieldNotes/Conditions
UIDrecord.uid
NATIVE CHARACTER NAMESrecord.nameInformation.nameDetails.details.valuerole = wcNameRole:STRING_NAME -and-
relations.value = wcNameType:AKA -and-
relations.value = true where rel = wcRelatedRel:IS_NON_LATIN_NAME

Deleted Profiles File​

The table below provides a quick view of the mapping between legacy World-Check Data File fields from the Deleted Profiles file and World-Check On Demand objects. Click the legacy field names for more details.

World-Check Data (Deleted Profiles) File Record FieldWorld-Check On Demand Object/FieldNotes/Conditions
UIDrecord.uid
DATErecord.recordDateInformation.recordDateDetails.details.valuetype = wcRecordDateType:DELETION_DATE

Legacy Field Attribute​

World-Check On Demand concepts with direct equivalents in World-Check Data File (WCDF) has an attribute in the concept.relateds array where rel = wcMdRelatedRel:hasLegacyDF1.0Value. The value within this object is the equivalent legacy value in WCDF.

World-Check On Demand Concept record for the Entity record type showing the legacy mapping information.
"concept": {
    "created": "2022-05-12T00:00:00.000Z",
    "modified": "2025-05-02T07:43:10.095Z",
    "effectiveFrom": "2022-05-12T00:00:00.000Z",
    "id": "wcRecordType:ENT", <-------------
    .
    .
    .
    "names": [
        {
            "role": "wcMdNameRole:MAIN_NAME",
            "language": "en-GB",
            "value": "Entity", <-------------
            "created": "2022-05-12T00:00:00.000Z",
            "effectiveFrom": "2022-05-12T00:00:00.000Z"
        }
    ],
    "definitions": [...],
    "relateds": [
        {
            "created": "2022-05-12T00:00:00.000Z",
            "modified": "2025-05-02T07:43:12.348Z",
            "effectiveFrom": "2022-05-12T00:00:00.000Z",
            "rel": "wcMdRelatedRel:hasLegacyDF1.0Value", <-------------
            "value": "E", <-------------
            "valueDataType": "wcDataType:STRING"
        }
    ]
},

Other examples:

World-Check On Demand ConceptWorld-Check Data File FieldWorld-Check Data File Value
wcCat2:CRIME_FINANCIALCATEGORYCRIME - FINANCIAL
wcCat3:CRRPT1SPECIAL INTEREST CATEGORIESBribery and Corruption
wcGenderDetail:FEMALEE/IF
wcSourceKwd:UKHMTKEYWORDSUKHMT
wcLocationType:BIRTH_LOCATIONPLACE OF BIRTHthe actual value
tip

Additional entries in World-Check On Demand may be added over time. Please refer to the Reference API content for the latest entries.

Legacy Fields​

UID​

ProductField or Value / Record Area
World-Check Data FileUID
World-Check On Demandrecord.uid

The record UID in World-Check On Demand is directly inheriting the same values from World-Check Data File for the same records with no change in formatting or data type.

LAST NAME​

All names of the record subject are contained within the nameInformation record area in World-Check On Demand, whether these are primary or aliases, or written in Latin or non-Latin scripts. There are attributes within each name object that help identify these different properties. Please see the Name Information details in the Record Data Features.

ProductField or Value / Record Area
World-Check Data FileLASTNAME
World-Check On Demandrecord.nameInformation.nameDetails.details.value

The legacy LASTNAME field is a mandatory field and holds the lastname for individuals or primary names for entities. In World-Check On Demand, the value of this field is mapped to a similar object within the record.nameInformation.nameDetails.details array, but with these key attributes:

  • when the record type is an Individual:
    • nameDetails.details array object will have a role = wcNameRole:LAST_NAME, which is the direct equivalent
    • there will also be an entry within the same nameDetails.details array object where role = wcNameRole:STRING_NAME, representing the full name as a string
    • in most cases, there will be another entry where role = wcNameRole:FIRST_NAME
An example of a Name Information entry for an individual.
"nameInformation": {
    "nameDetails": [
        {
            "id": "f395c235609acefefbdd4b3e0cd58d9c",
            "isDefault": true, <-------------
            "details": [
                {
                    "role": "wcNameRole:STRING_NAME",
                    "value": "Jardani JOVONOVICH",
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcNameRole:FIRST_NAME",
                    "value": "Jardani",
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcNameRole:LAST_NAME", <-------------
                    "value": "KHAN",
                    "valueDataType": "wcDataType:STRING"
                },
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                    "value": "wcNameType:PRIMARY", <-------------
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
            ],
  • when the record type is a non-Individual (i.e., Entity, Vessel, Aircraft, Website, Port, Geography):
    • details array object will have a role = wcNameRole:STRING_NAME representing the as-reported name and will not have the FIRST_NAME or LAST_NAME name role
An example of a Name Information entry for a non-individual.
"nameInformation": {
   "nameDetails": [
       {
           "id": "f395c235609acefefbdd4b3e0cd58d5b",
           "isDefault": true, <-------------
           "details": [
               {
                   "role": "wcNameRole:STRING_NAME", <-------------
                   "value": "The Continental",
                   "valueDataType": "wcDataType:STRING"
               },
           "relations": [
               {
                   "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                   "value": "wcNameType:PRIMARY", <-------------
                   "valueDataType": "wcDataType:Q_CODE"
               }
           ]
           ],
  • whether Individual or non-Individual, the LAST NAME equivalent in World-Check On Demand will have:
    • nameDetails.isDefault = true; there is only one nameInformation entry with this value
    • nameDetails.relations.value = wcNameType:PRIMARY where rel = wcRelatedRel:HAS_WC_NAME_TYPE; there could also be other name types

FIRST NAME​

Similar to the legacy LAST NAME, this is mapped to entries within the nameInformation record area in World-Check On Demand.

ProductField or Value / Record Area
World-Check Data FileFIRSTNAME
World-Check On Demandrecord.nameInformation.nameDetails.details.value

Unlike the LAST NAME entry, the legacy FIRST NAME is only present for individual record types. Other required attributes:

  • nameDetails.isDefault = true as there is only one nameInformation entry with this value
  • nameDetails.relations.value = wcNameType:PRIMARY where rel = wcRelatedRel:HAS_WC_NAME_TYPE; there could also be other name types

Please see the previous example on LAST NAME mapping for Individual record types.

ALIASES​

ProductField or Value / Record Area
World-Check Data FileALIAS
World-Check On Demandrecord.nameInformation.nameDetails.details.value
An example of a Name Information entry for an individual's alias.
"nameInformation": {
    "nameDetails": [
        {
            "id": "f395c235609acefefbdd4b3e0cd58d9c",
            "details": [
                {
                    "role": "wcNameRole:STRING_NAME",
                    "value": "John WICK", <-------------
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                    "value": "wcNameType:AKA", <-------------
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
            ],

The names in ALIASES are also mapped to entries in nameInformation, with some key differences:

  • equivalent entries in nameInformation will only have a string equivalent and are not broken into first name and last names for individuals; breaking alias and low-quality alias strings into name components is part of the data enrichment roadmap
  • nameDetails.isDefault = false or is not present in the nameDetails object
  • nameDetails.relations.value = wcNameType:AKA where rel = wcRelatedRel:HAS_WC_NAME_TYPE; there could also be other name types

LOW QUALITY ALIASES​

ProductField or Value / Record Area
World-Check Data FileLOW QUALITY ALIAS
World-Check On Demandrecord.nameInformation.nameDetails.details.value
An example of a Name Information entry for an individual where it is an alias according to one source and low-quality alias for another source.
"nameInformation": {
    "nameDetails": [
        {
            "id": "f395c235609acefefbdd4b3e0cd58d8a",
            "details": [
                {
                    "role": "wcNameRole:STRING_NAME",
                    "value": "The Bogeyman", <-------------
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                    "value": "wcNameType:AKA", <-------------
                    "valueDataType": "wcDataType:Q_CODE",
                    "relations": [
                        {
                            "rel": "wcRelatedRel:AS_REPORTED_BY_KEYWORD", <-------------
                            "value": "f2f622adbfd017d8c7dd5ede395dcdff",
                            "valueDataType": "wcDataType:IDREF"
                        }
                    ]
                },
                {
                    "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                    "value": "wcNameType:LQA", <-------------
                    "valueDataType": "wcDataType:Q_CODE",
                    "relations": [
                        {
                            "rel": "wcRelatedRel:AS_REPORTED_BY_KEYWORD", <-------------
                            "value": "28cf0b69d0d5465de43de1e445c008ae",
                            "valueDataType": "wcDataType:IDREF"
                        }
                    ]
                }
            ]
            ],

The names in LOW QUALITY ALIAS are also mapped to entries in nameInformation, with some key differences:

  • equivalent entries in nameInformation will only have a string equivalent and are not broken into first name and last names for individuals; breaking alias and low-quality alias strings into name components is part of the data enrichment roadmap
  • nameDetails.isDefault = false or will not be present
  • nameDetails.relations.value = wcNameType:LQA where rel = wcRelatedRel:HAS_WC_NAME_TYPE; there could also be other name types

ALTERNATIVE SPELLING​

ProductField or Value / Record Area
World-Check Data FileALTERNATIVE SPELLING
World-Check On Demandrecord.nameInformation.nameDetails.details.value

Entries in ALTERNATIVE SPELLING has been progressively migrated to the ALIAS field for some time now. Any name that remains on this field is mapped similar to the ALIASES legacy field.

CATEGORY​

There is new record categorisation taxonomy in World-Check On Demand. The legacy values found in the CATEGORY field are now mapped to different data points in World-Check On Demand.

ProductField or Value / Record Area
World-Check Data FileCATEGORY
World-Check On Demandrecord.recordType.value -or-
record.recordType.recordSubTypes.value -or-
record.categoryInformation.categories.categoryPath

Most of the legacy CATEGORY entries are now record sub-types in World-Check On Demand, while others map to record types:

World-Check Data File CATEGORYWorld-Check On Demand Record Sub-TypeWorld-Check On Demand Record Type
BANKwcRecordSubType:BANK wcRecordType:ENT
CORPORATEwcRecordSubType:CORPORATEwcRecordType:ENT
POLITICAL PARTY wcRecordSubType:POLITICAL_PARTYwcRecordType:ENT
TRADE UNIONwcRecordSubType:TRADE_UNIONwcRecordType:ENT
SHELL BANK OR COMPANYwcRecordSubType:SHELL_BANK_COMPANYwcRecordType:ENT
ORGANISATIONwcRecordSubType:ORGANIZATIONwcRecordType:ENT
EMBARGOwcRecordSubType:EMBARGO_COUNTRYwcRecordType:GEO
COUNTRYwcRecordSubType:RISK_COUNTRYwcRecordType:GEO
SPECIAL JURISDICTIONwcRecordSubType:SPECIAL_JURISDICTIONwcRecordType:GEO
ADDRESSwcRecordSubType:ADDRESS wcRecordType:GEO
LEGALwcRecordSubType:LEGALwcRecordType:IND
MILITARYwcRecordSubType:MILITARYwcRecordType:IND
DIPLOMATwcRecordSubType:DIPLOMAT wcRecordType:IND
POLITICAL INDIVIDUALwcRecordSubType:POLITICAL_INDIVIDUALwcRecordType:IND
RELIGIONwcRecordSubType:RELIGIONwcRecordType:IND
INDIVIDUALwcRecordSubType:INDIVIDUALwcRecordType:IND
CRIME - FINANCIAL
CRIME - NARCOTICS
CRIME - ORGANIZED
CRIME - OTHER
CRIME - TERROR
CRIME - WAR		wcRecordSubType:POST_CONwcRecordType:IND
EMBARGO AIRCRAFTwcRecordSubType:EMBARGO_AIRCRAFTwcRecordType:ARCFT
AIRCRAFTwcRecordSubType:SANC_EMBARGO_AIRCRAFT
wcRecordSubType:SPECIAL_INT_AIRCRAFT		wcRecordType:ARCFT
EMBARGO VESSELwcRecordSubType:EMBARGO_VESSELwcRecordType:VESL
VESSELwcRecordSubType:SANC_EMBARGO_VESSEL
wcRecordSubType:SPECIAL_INT_VESSEL
wcRecordSubType:VESSEL		wcRecordType:VESL
PORTwcRecordSubType:AIRPORT
wcRecordSubType:SEAPORT		wcRecordType:PORT
WEBSITEN/AwcRecordType:WEB

At the same time, some of the CATEGORY values also map to the new category taxonomy entries in World-Check On Demand:

World-Check Data File CATEGORYWorld-Check On Demand Category
CRIME - FINANCIALwcCat2:CRIME_FINANCIAL
CRIME - NARCOTICSwcCat2:CRIME_NARCOTICS
CRIME - ORGANIZEDwcCat2:CRIME_ORGANIZED
CRIME - OTHERwcCat2:CRIME_OTHER
CRIME - TERRORwcCat2:CRIME_TERROR
CRIME - WARwcCat2:CRIME_WAR

TITLE​

Similar to the legacy FIRST NAME, this is mapped to entries within the nameInformation record area in World-Check On Demand.

ProductField or Value / Record Area
World-Check Data FileTITLE
World-Check On Demandrecord.nameInformation.nameDetails.details.value

Unlike in World-Check Data File, titles in World-Check On Demand are independent of specific names. This means that titles can be logically combined with any of the names of the record subject.

An example of a Name Information entry with two names and a title.
"nameInformation": {
    "nameDetails": [
        {
            "id": "f395c235609acefefbdd4b3e0cd58d9c",
            "isDefault": true,
            "details": [
                {
                    "role": "wcNameRole:STRING_NAME",
                    "value": "Stephen Vincent STRANGE", <-------------
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcNameRole:FIRST_NAME",
                    "value": "Stephen Vincent",
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcNameRole:LAST_NAME",
                    "value": "STRANGE",
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                    "value": "wcNameType:PRIMARY",
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
        },
        {
            "id": "f395c235609acefefbdd4b3e0cd58d9d",
            "details": [
                {
                    "role": "wcNameRole:STRING_NAME",
                    "value": "Strange", <-------------
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_WC_NAME_TYPE",
                    "value": "wcNameType:AKA",
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
        },
        {
            "id": "4621b01c74d9743d32511a6b4d525c31",
            "details": [
                {
                    "role": "wcNameRole:SINGLE_TITLE",
                    "value": "wcTitlePrefix:DR",  <-------------
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
        },

In the above example, the title with a friendly name of Dr can be combined with primary and alias names when doing screenings as it is not bound to a specific name entry:

  • Dr Stephen Vincent STRANGE
  • Dr Strange

Like the legacy FIRST NAME field, this is only present for individual record types. The legacy TITLE is mapped to either one these two possible name roles in World-Check On Demand:

  • nameDetails.details.role = wcNameRole:SINGLE_TITLE
  • nameDetails.details.role = wcNameRole:SINGLE_TITLE_AS_IS

The other available title concepts in World-Check On Demand are reserved for future use.

SUB-CATEGORY​

The legacy SUB-CATEGORY field are all about Politically Exposed Persons and State-related entities. These are mapped to the new categorisation taxonomy in World-Check On Demand.

ProductField or Value / Record Area
World-Check Data FileSUB-CATEGORY
World-Check On Demandrecord.categoryInformation.categories.categoryPath

This table shows the legacy CATEGORY entries and how it is mapped to category entries in World-Check On Demand.

World-Check Data File CATEGORYWorld-Check On Demand Category 2World-Check On Demand Category 1
PEP IOwcCat2:PEP_IOwcCat1:POLITICALLY_EXPOSED
PEP ROwcCat2:PEP_ROwcCat1:POLITICALLY_EXPOSED
PEP NwcCat2:PEP_NwcCat1:POLITICALLY_EXPOSED
PEP SNwcCat2:PEP_SNwcCat1:POLITICALLY_EXPOSED
PEP LwcCat2:PEP_LwcCat1:POLITICALLY_EXPOSED
PEP NGwcCat2:PEP_NGwcCat1:POLITICALLY_EXPOSED
PEP L-AwcCat2:PEP L-AwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP L-RwcCat2:PEP L-RwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP L-AEwcCat2:PEP L-AEwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP N-AEwcCat2:PEP N-AEwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP N-AwcCat2:PEP N-AwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP N-RwcCat2:PEP N-RwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP RO-AEwcCat2:PEP RO-AEwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP RO-AwcCat2:PEP RO-AwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP RO-RwcCat2:PEP RO-RwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP SN-AEwcCat2:PEP SN-AEwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP SN-AwcCat2:PEP SN-AwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP SN-RwcCat2:PEP SN-RwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP NG-AEwcCat2:PEP NG-AEwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP NG-AwcCat2:PEP NG-AwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
PEP NG-RwcCat2:PEP NG-RwcCat1:RELATIVES_CLOSE_ASSOCIATIONS
IOSwcCat2:IOSwcCat1:STATE_OWNED
SIEwcCat2:SIEwcCat1:STATE_OWNED
SOE LwcCat2:SOE_LwcCat1:STATE_OWNED
SOE NwcCat2:SOE_NwcCat1:STATE_OWNED
SOE SNwcCat2:SOE_SNwcCat1:STATE_OWNED
SOEwcCat2:SOEwcCat1:STATE_OWNED
tip

Additional entries in World-Check On Demand may be added over time. Please refer to the Reference API content for the latest entries.

POSITION​

Each PEP Role entry in World-Check On Demand has a position object. The entry that maps back to the legacy POSITION field in World-Check Data File is the position value for the latest PEP role.

ProductField or Value / Record Area
World-Check Data FilePOSITION
World-Check On Demandrecord.pepRoleInformation.pepRoleDetails.position.value
A PEP Role entry in World-Check On Demand where the record subject's position is a Member of Legislature.
"pepRoleInformation": {
    "status": {
        "value": "wcStatus:ACTIVE",
        "valueDataType": "wcDataType:Q_CODE"
    },
    "pepRoleDetails": [
        {
            "effectiveFrom": {
                "status": {
                    "value": "wcStatus:CONFIRMED"
                },
                "value": "2024-05" <-------------
            },
            "id": "4ac8ced4e6daaadc75edec30087c7342",
            "level": {
                "value": "wcPEPRoleLevel:NATIONAL",
                "valueDataType": "wcDataType:Q_CODE"
            },
            "locationInformation": {
                .
                .
                .
            },
            "position": {
                "value": "wcPepPosition:MEMLEG", <-------------
                "valueDataType": "wcDataType:Q_CODE"
            },
            "role": {
                "value": "wcPepRole:MEM_OF_SENATE",
                "valueDataType": "wcDataType:Q_CODE"
            },
            "roleBiography": [
                {
                    "value": "Senator of Chandrila",
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "status": {
                "value": "wcStatus:CURRENT",
                "valueDataType": "wcDataType:Q_CODE"
            }
        }
    ],
},

The pepRoleDetails.effectiveFrom.value is used to determine the PEP role effectivity timing.

AGE​

ProductField or Value / Record Area
World-Check Data FileAGE and AGE DATE (AS OF DATE)
World-Check On Demandrecord.dateInformation.dateDetails.details.value

The legacy AGE and AGE DATE (AS OF DATE) fields are not directly mapped to any World-Check On Demand data points. Instead of the numeric age, World-Check On Demand offers calculated years of birth.

A Date Information entry showing calculated years of birth.
"dateInformation": {
    "dateDetails": [
        {
            "type": "wcDateType:CALCULATED_YOB",
            "details": [
                {
                    "role": "wcDateRole:MIN_DATE",
                    "validatedFormat": true,
                    "value": "2002",
                    "valueDataType": "wcDataType:DATE"
                },
                {
                    "role": "wcDateRole:MAX_DATE",
                    "validatedFormat": true,
                    "value": "2003",
                    "valueDataType": "wcDataType:DATE"
                }
            ],
            "id": "a74055dc9aa52a04e6488f6fcc1a1059",
            "isDefault": true
        }
    ]
},

The legacy AGE and AGE DATE (AS OF DATE) are now represented by a minimum and maximum years of birth.

DOB​

Most date-related information about the record subject are located in the dateInformation record area in World-Check On Demand.

ProductField or Value / Record Area
World-Check Data FileDOB
World-Check On Demandrecord.dateInformation.dateDetails.details.value

The legacy DOB field values are mapped to entries within the dateInformation record area, specifically with these additional attributes:

  • dateDetails.type = wcDateType:REPORTED_DOB
  • dateDetails.isDefault = true
A Date Information entry showing the default Date of Birth.
"dateInformation": {
    "dateDetails": [
        {
            "type": "wcDateType:REPORTED_DOB", <-------------
            "details": [
                {
                    "role": "wcDateRole:VALUE",
                    "validatedFormat": true,
                    "value": "1994-10-12", <-------------
                    "valueDataType": "wcDataType:DATE"
                }
            ],
            "id": "b878c253e88a84e8cc2ddf7e3806fc78",
            "isDefault": true <-------------
        }
    ]
},

The value can take on any of the standard date formats for date of birth.

DOBS​

ProductField or Value / Record Area
World-Check Data FileDOBS
World-Check On Demandrecord.dateInformation.dateDetails.details.value

The legacy DOBS field values are mapped to entries within the dateInformation record area, specifically with these additional attributes:

  • dateDetails.type = wcDateType:REPORTED_DOB
  • dateDetails.isDefault = false or is not present within the dateDetails object
A Date Information entry showing the non-default Dates of Birth.
"dateInformation": {
    "dateDetails": [
        {
            "type": "wcDateType:REPORTED_DOB", <-------------
            "details": [
                {
                    "role": "wcDateRole:VALUE",
                    "validatedFormat": true,
                    "value": "1994-10", <-------------
                    "valueDataType": "wcDataType:DATE"
                }
            ],
            "id": "b878c253e88a84e8cc2ddf7e3806fc79",
        },
        {
            "type": "wcDateType:REPORTED_DOB", <-------------
            "details": [
                {
                    "role": "wcDateRole:VALUE",
                    "validatedFormat": true,
                    "value": "1994", <-------------
                    "valueDataType": "wcDataType:DATE"
                }
            ],
            "id": "b878c253e88a84e8cc2ddf7e3806fc80",
        }
    ]
},

The value can take on any of the standard date formats for date of birth.

PLACE OF BIRTH​

Details regarding locations of the record subject are placed in the locationInformation record area in World-Check On Demand, including the legacy PLACE OF BIRTH.

ProductField or Value / Record Area
World-Check Data FilePLACE OF BIRTH
World-Check On Demandrecord.locationInformation.locationDetails.details.value
An example of a Location Information entry with Place Of Birth.
"locationInformation": {
    "locationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc81",
            "type": "wcLocationType:BIRTH_LOCATION", <-------------
            "details": [
                {
                    "role": "wcLocationRole:STRING_LOCATION", 
                    "value": "New York, United States", <-------------
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcLocationRole:COUNTRY",
                    "value": "wcCountry:US",
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
        }

The legacy PLACE OF BIRTH field values are mapped to entries within the locationInformation record area, specifically with these additional attributes:

  • locationDetails.type = wcLocationType:BIRTH_LOCATION
  • locationDetails.details.role = wcLocationRole:STRING_LOCATION

World-Check On Demand also provides a structured country information. This is found on the locationDetails.details object where role = wcLocationRole:COUNTRY.

DECEASED​

ProductField or Value / Record Area
World-Check Data FileDECEASED
World-Check On Demandrecord.dateInformation.dateDetails.details.value

Similar to other record date information, the legacy DECEASED details are placed in the dateInformation record area in World-Check On Demand.

An example of a Date Information entry showing Deceased Date.
"dateInformation": {
    "dateDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc82",
            "type": "wcDateType:DECEASED_DATE", <-------------
            "details": [
                {
                    "role": "wcDateRole:VALUE",
                    "validatedFormat": true,
                    "value": "2023-12-31", <-------------
                    "valueDataType": "wcDataType:DATE"
                }
            ],
        }

The legacy DECEASED field values are mapped to entries within the dateInformation record area, specifically with these additional attributes:

  • dateDetails.type = wcDateType:DECEASED_DATE
  • dateDetails.details.role = wcDateRole:VALUE

The value can take on any of the standard date formats for deceased date.

PASSPORTS​

ProductField or Value / Record Area
World-Check Data FilePASSPORTS
World-Check On Demandrecord.identificationInformation.identificationDetails.details.value

Passport details can be found in the identificationInformation record area in World-Check On Demand, along with other identification documents.

An example of an Identification Information entry showing a passport.
"identificationInformation": {
    "identificationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc83",
            "type": "wcIdentificationType:PASSPORT", <-------------
            "details": [
                {
                    "role": "wcIdentificationRole:VALUE",
                    "value": "P1234567", <-------------
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcIdentificationRole:ISSUING_COUNTRY",
                    "value": "wcCountry:US", <-------------
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
        }

The legacy PASSPORTS field values are mapped to entries within the identificationInformation record area, specifically with these additional attributes:

  • identificationDetails.type = wcIdentificationType:PASSPORT
  • identificationDetails.details.role = wcIdentificationRole:VALUE for the passport number
  • identificationDetails.details.role = wcIdentificationRole:ISSUING_COUNTRY for the issuing country

SSN​

ProductField or Value / Record Area
World-Check Data FileSSN
World-Check On Demandrecord.identificationInformation.identificationDetails.details.value

Similar to other identification details, Social Security Numbers (SSN) are now part of the identificationInformation record area in World-Check On Demand. The SSN type value will depend on the country of issuance, with wcIdentificationType:US_SSN being the most common.

An example of an Identification Information entry showing a US SSN.
"identificationInformation": {
    "identificationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc84",
            "type": "wcIdentificationType:US_SSN", <-------------
            "details": [
                {
                    "role": "wcIdentificationRole:VALUE",
                    "value": "123-45-6789", <-------------
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcIdentificationRole:ISSUING_COUNTRY",
                    "value": "wcCountry:US", <-------------
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
        }

The legacy SSN field values are mapped to entries within the identificationInformation record area, specifically with these additional attributes:

  • identificationDetails.type = one of the many country-specific SSN-type concepts, such as the wcIdentificationType:US_SSN for US Social Security Numbers
  • identificationDetails.details.role = wcIdentificationRole:VALUE for the SSN value
  • identificationDetails.details.role = wcIdentificationRole:ISSUING_COUNTRY for the issuing country

IDENTIFICATION NUMBERS​

ProductField or Value / Record Area
World-Check Data FileIDENTIFICATION NUMBERS
World-Check On Demandrecord.identificationInformation.identificationDetails.details.value

Similar to passports and SSNs, other identification numbers are part of the identificationInformation record area in World-Check On Demand.

An example of an Identification Information entry showing a company registration number issued by the Securities and Exchange Commission of the Philippines.
"identificationInformation": {
    "identificationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc85",
            "type": "wcIdentificationType:PH_SEC", <-------------
            "details": [
                {
                    "role": "wcIdentificationRole:VALUE",
                    "value": "CN123456789", <-------------
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcIdentificationRole:ISSUING_COUNTRY",
                    "value": "wcCountry:PH", <-------------
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
        }

The legacy IDENTIFICATION NUMBERS field values are mapped to entries within the identificationInformation record area, specifically with these additional attributes:

  • identificationDetails.type = one of many identification type concepts
  • identificationDetails.details.role = wcIdentificationRole:VALUE for the identification number
  • identificationDetails.details.role = wcIdentificationRole:ISSUING_COUNTRY for the issuing country when applicable

Each identification type has its own specific concept in World-Check On Demand, making it easier to filter and search for specific types of identification numbers.

LOCATIONS​

ProductField or Value / Record Area
World-Check Data FileLOCATIONS
World-Check On Demandrecord.locationInformation.locationDetails.details.value

Location details are found in the locationInformation record area in World-Check On Demand. All legacy LOCATIONS field values will have an undetermined location type in World-Check On Demand and are mapped to structured and specific location types when such details are available.

An example of Location Information entries showing different location types.
"locationInformation": {
    "locationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc86",
            "type": "wcLocationType:UNDETERMINED_LOCATION", <-------------
            "details": [
                {
                    "role": "wcLocationRole:STRING_LOCATION", <-------------
                    "value": "Akron, New York, United States", 
                    "valueDataType": "wcDataType:STRING"
                },
                {
                    "role": "wcLocationRole:COUNTRY", <-------------
                    "value": "wcCountry:US",
                    "valueDataType": "wcDataType:Q_CODE"
                },
                {
                    "role": "wcLocationRole:STATE_PROVINCE", <-------------
                    "value": "wcStateProvince:US_NEW_YORK",
                    "valueDataType": "wcDataType:Q_CODE"
                },
                {
                    "role": "wcLocationRole:CITY", <-------------
                    "value": "wcCityList:AKRON_NEW_YORK_USA",
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
        }

The legacy LOCATIONS field values are mapped to entries within the locationInformation record area, specifically with these additional attributes:

  • locationDetails.type = wcLocationType:UNDETERMINED_LOCATION as they were not associated with any specific location type when originally captured
  • locationDetails.details.role = wcLocationRole:STRING_LOCATION for the unstructured location string
  • locationDetails.details.role = wcLocationRole:COUNTRY for the country
  • locationDetails.details.role = wcLocationRole:STATE_PROVINCE for the state or province when available
  • locationDetails.details.role = wcLocationRole:CITY for the city when available

World-Check On Demand provides more structured location information compared to the legacy string values, making it easier to filter and search for specific location components.

COUNTRIES​

ProductField or Value / Record Area
World-Check Data FileCOUNTRIES
World-Check On Demandrecord.locationInformation.locationDetails.details.value

Similar to other location details, country information can be found in the locationInformation record area in World-Check On Demand. The main country of citizenship will have a specific default flag.

An example of a Location Information entry showing a primary country of citizenship.
"locationInformation": {
    "locationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc87",
            "type": "wcLocationType:CITIZENSHIP_LOCATION", <-------------
            "details": [
                {
                    "role": "wcLocationRole:COUNTRY", <-------------
                    "value": "wcCountry:US", 
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
            "isDefault": true <-------------
        }

The legacy COUNTRIES field values are mapped to entries within the locationInformation record area, specifically with these additional attributes:

  • locationDetails.type = wcLocationType:CITIZENSHIP_LOCATION
  • locationDetails.details.role = wcLocationRole:COUNTRY
  • locationDetails.isDefault = true

CITIZENSHIP​

ProductField or Value / Record Area
World-Check Data FileCITIZENSHIP
World-Check On Demandrecord.locationInformation.locationDetails.details.value
An example of a Location Information entry showing a secondary country of citizenship.
"locationInformation": {
    "locationDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc88",
            "type": "wcLocationType:CITIZENSHIP_LOCATION", <-------------
            "details": [
                {
                    "role": "wcLocationRole:COUNTRY", <-------------
                    "value": "wcCountry:GB", 
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ],
        }

Similar to the legacy COUNTRIES field values, the legacy CITIZENSHIP field values are mapped to entries within the locationInformation record area, specifically with these additional attributes:

  • locationDetails.type = wcLocationType:CITIZENSHIP_LOCATION
  • locationDetails.details.role = wcLocationRole:COUNTRY
  • locationDetails.isDefault = false or is not present within the locationDetails object

COMPANIES​

ProductField or Value / Record Area
World-Check Data FileCOMPANIES
World-Check On Demandrecord.connectionInformation.connectionDetails.value

The legacy COMPANIES are specifically the non-individual entries in connectionInformation record area. Individual entries are those from the legacy LINKED TO field (see below).

An example of a Connection Information entry showing a company associations.
"connectionInformation": {
    "connectionDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc89",
            "type": "wcRecordType:ENT", <-------------
            "value": "The Continental", 
            "valueDataType": "wcDataType:STRING", <-------------
        },
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc89",
            "type": "wcRecordType:ENT", <-------------
            "value": "987654", 
            "valueDataType": "wcDataType:UID", <-------------
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_CONNECTION_DIRECTION",
                    "value": "wcConnectionDirectionType:UNI_DIR",
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
        }

The legacy COMPANIES field values are mapped to entries within the connectionInformation record area, specifically with these additional attributes:

  • connectionDetails.type must not be equal to wcRecordType:IND (individual)
  • connectionDetails.valueDataType = wcDataType:UID when the connected organisation has a World-Check record
  • connectionDetails.valueDataType = wcDataType:STRING when the connected organisation does not have a presence in World-Check

Connection Information entries in World-Check On Demand also includes relationship directionality (e.g., unidirectional or bidirectional) based on the connection details in the related World-Check record.

E/I​

ProductField or Value / Record Area
World-Check Data FileE/I
World-Check On Demandrecord.recordType.value -or-
record.genderInformation.genderDetails.details.value

The legacy E/I field is used to indicate the gender of the record subject (when available) or if the record subject is not an individual (i.e., entity).

An example of a Gender Information entry.
"genderInformation": {
    "genderDetails": [
    {
        "id": "b878c253e88a84e8cc2ddf7e3806fc90",
        "details": [
        {
            "role": "wcGenderRole:VALUE",
            "value": "wcGenderDetail:FEMALE",
            "valueDataType": "wcDataType:Q_CODE"
        }
        ]
    }

The legacy E/I values are mapped to different record areas in World-Check On Demand depending on what they represent:

When the legacy E/I = E, this maps to:

  • record.recordType.value = wcRecordType:ENT indicating this is an entity record

When the legacy E/I = M or F, this maps to:

  • record.genderInformation.genderDetails.details.value where:
    • value = wcGenderDetail:MALE for M
    • value = wcGenderDetail:FEMALE for F

World-Check On Demand supports more gender values than World-Check Data File.

LINKED TO​

ProductField or Value / Record Area
World-Check Data FileLINKED TO
World-Check On Demandrecord.connectionInformation.connectionDetails.value

In contrast to the legacy COMPANIES entries, the legacy LINKED TO entries map to individual records in connectionInformation record area.

An example of a Connection Information entry showing individual associations.
"connectionInformation": {
    "connectionDetails": [
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc89",
            "type": "wcRecordType:IND", <-------------
            "value": "John Wick", 
            "valueDataType": "wcDataType:STRING", <-------------
        },
        {
            "id": "b878c253e88a84e8cc2ddf7e3806fc89",
            "type": "wcRecordType:IND", <-------------
            "value": "123456", 
            "valueDataType": "wcDataType:UID", <-------------
            "relations": [
                {
                    "rel": "wcRelatedRel:HAS_CONNECTION_DIRECTION",
                    "value": "wcConnectionDirectionType:BI_DIR",
                    "valueDataType": "wcDataType:Q_CODE"
                }
            ]
        }

The legacy LINKED TO field values are mapped to entries within the connectionInformation record area, specifically with these additional attributes:

  • connectionDetails.type = wcRecordType:IND (individual)
  • connectionDetails.valueDataType = wcDataType:UID when the connected individual has a World-Check record
  • connectionDetails.valueDataType = wcDataType:STRING when the connected individual does not have a presence in World-Check

Connection Information entries in World-Check On Demand also includes relationship directionality (e.g., unidirectional or bidirectional) based on the connection details in the related World-Check record.

FURTHER INFORMATION​

ProductField or Value / Record Area
World-Check Data FileFURTHER INFORMATION
World-Check On Demandrecord.furtherInformation.furtherDetails.details.value

The Further Information details are largely unchanged and are mapped to the furtherInformation record area in World-Check On Demand.

An example showing multiple Further Information entries.
"furtherInformation": {
    "furtherDetails": [
        {
            "details": [
                {
                    "role": "wcFurtherInformation:REPORTS", <-------------
                    "value": "Jan 2025 - reportedly suspended by the Securities Commission for non-filing of reportorial requirements.",
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "id": "ed23719aa242e262f49060d82433943ae9"
        },
        {
            "details": [
                {
                    "role": "wcFurtherInformation:BIOGRAPHY", <-------------
                    "value": "Deputy Minister of Cities, Local Government and Public Works for Republic of Wakanda (Nov 2022 - ).",
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "id": "d524068b7007a1d4e81571c4fe284b5b"
        }
    ]
},

Each concatenated entry within the legacy FURTHER INFORMATION are now elements of the furtherDetails array with the role value of each element indicating the heading information for the entry.

Note that Reports with no further information reported are not returned in World-Check On Demand.

KEYWORDS​

ProductField or Value / Record Area
World-Check Data FileKEYWORDS
World-Check On Demandrecord.keywordReferenceList.keywordTag.keyword

The legacy KEYWORDS values map into the keywordReferenceList record area of World-Check On Demand.

An example showing multiple keywords with effectivity timestamps and status.
"keywordReferenceList": [
    {
        "keywordTag": {
            "currentFrom": "2022-08-21T17:19:33.56Z",
            "id": "e565ab37c87935c1f9d3f7864f3825e1",
            "keyword": "wcSourceKwd:OFAC", <-------------
            "status": {
                "value": "wcStatus:CURRENT",
                "valueDataType": "wcDataType:Q_CODE"
            }
        }
    },
    {
        "keywordTag": {
            "currentFrom": "2022-08-21T17:19:33.56Z",
            "currentTo": "2025-07-15T19:35:02Z",
            "id": "e565ab37c87935c1f9d3f7864f3825e1",
            "keyword": "wcSourceKwd:UKHMT", <-------------
            "status": {
                "value": "wcStatus:FORMER",
                "valueDataType": "wcDataType:Q_CODE"
            }
        }
    }
],

World-Check On Demand also provides additional information such as the effectivity timestamps and the overall status.

EXTERNAL SOURCES​

ProductField or Value / Record Area
World-Check Data FileEXTERNAL SOURCES
World-Check On Demandrecord.sourceReferenceList.sourceRefs.value

The legacy EXTERNAL SOURCES values map into the sourceReferenceList record area of World-Check On Demand.

A Source Reference List sample showing multiple URLs.
"sourceReferenceList": {
    "sourceRefs": [
        {
            "id": "c14a94d59f46016ca7ff371925edfb5d",
            "details": [
                {
                    "role": "wcDateRole:URL_ADDITION_DATE",
                    "value": "2025-08-21T08:22:36.217Z",
                    "valueDataType": "wcDataType:DATETIME"
                }
            ],
            "type": "wcResourceType:SOURCE_DATA",
            "role": "wcResourceRole:RESOURCE_REF",
            "value": "https://www.somerandomwebsite23909sdf8092090dfljae009dfadsf.com", <-------------
            "valueDataType": "wcDataType:ANYURI"
        },
        {
            "id": "59d52bf23c9f5a8b720a04d998d69574",
            "details": [
                {
                    "role": "wcDateRole:URL_ADDITION_DATE",
                    "value": "2024-12-31T10:11:25.889Z",
                    "valueDataType": "wcDataType:DATETIME"
                }
            ],
            "type": "wcResourceType:SOURCE_DATA",
            "role": "wcResourceRole:RESOURCE_REF",
            "value": "https://www.someotherrandomwebsite99a8fp993jasdof8yaehudsfh.com", <-------------
            "valueDataType": "wcDataType:ANYURI"
        }
    ]
},

UPDATE CATEGORY​

ProductField or Value / Record Area
World-Check Data FileUPDATE CATEGORY
World-Check On DemandrecordMeta.changeHistory.updateCategory

The legacy UPDATE CATEGORY values map into the changeHistory of the World-Check On Demand recordMeta top-level object.

A Change History with multiple entries and the respective update category value on each.
"changeHistory": [
    {
        "publishedDate": "2024-08-06T00:00:00.000Z",
        "updateCategory": "wcUpdateCat:C6" <-------------
    },
    {
        "publishedDate": "2025-08-18T06:05:28.439Z",
        "updateCategory": "wcUpdateCat:C1", <-------------
        "added": [
            {
                "value": "wcChangeArea:FTHR_INFM",
                "valueDataType": "wcDataType:Q_CODE",
                "idRefs": [
                    "8560fb499956200080c6af8a35d7b0a1",
                    "ef026246b10c2b70aebcfb38a6343b96",
                    "19e59bf23f62e822fc5294c7006f4c47"
                ]
            }

World-Check On Demand records may contain one or more update categories in the changeHistory array depending on the following conditions:

  • record retrievals without the use of the lastPublishedDate filter will only return the latest changeHistory entry which contains the latest updateCategory value
  • record retrievals made with the lastPublishedDate filter may return more than one entry in changeHistory if there are multiple changes within the provided lookback period; each entry will have an updateCategory value

ENTERED​

ProductField or Value / Record Area
World-Check Data FileENTERED
World-Check On DemandrecordMeta.initialPublisheddate

The legacy ENTERED date values are mapped into the initialPublishedDate field of the equivalent World-Check On Demand record for all records published in World-Check Data File up to 8 August 2025. Past that date, records with the same UID will have slightly different values for ENTERED and initialPublishedDate as World-Check On Demand records are published earlier.

A record meta object in World-Check On Demand showing the initial published date.
"recordMeta": {
    "initialPublishedDate": "2022-12-08T00:00:00.000Z", <-------------
    "lastPublishedDate": "2025-08-18T12:40:45.127Z",
    "changeHistory": [
        {
            "publishedDate": "2024-08-06T00:00:00.000Z",
            "updateCategory": "wcUpdateCat:C6"
        },

UPDATED​

ProductField or Value / Record Area
World-Check Data FileUPDATED
World-Check On DemandrecordMeta.lastPublishedDate

The legacy UPDATED date values are mapped into the lastPublishedDate field of the equivalent World-Check On Demand record for all records published in World-Check Data File up to 8 August 2025. Past that date, records with the same UID will have slightly different values for UPDATED and lastPublishedDate as World-Check On Demand records are published earlier.

A record meta object in World-Check On Demand showing the last published date.
"recordMeta": {
    "initialPublishedDate": "2022-12-08T00:00:00.000Z",
    "lastPublishedDate": "2025-08-18T12:40:45.127Z", <-------------
    "changeHistory": [
        {
            "publishedDate": "2024-08-06T00:00:00.000Z",
            "updateCategory": "wcUpdateCat:C6"
        },

EDITOR​

This is not mapped to any public-facing World-Check On Demand field.

AGE DATE (AS OF DATE)​

ProductField or Value / Record Area
World-Check Data FileAGE DATE (AS OF DATE)
World-Check On Demandrecord.dateInformation.dateDetails.details.value

The legacy AGE and AGE DATE (AS OF DATE) fields are not directly mapped to any World-Check On Demand data points. Instead of the numeric age, World-Check On Demand offers calculated years of birth. Please see AGE above for more details.

PEP ROLES​

ProductField or Value / Record Area
World-Check Data FilePEP ROLES
World-Check On Demandrecord.pepRoleInformation.pepRoleDetails.role.value

Legacy PEP ROLES are mapped to entries within the pepRoleInformation record area in World-Check On Demand. Each concatenated entry in the legacy field is an element in the pepRoleDetails array.

An entry in the PEP Role Information showing a former Cabinet Minister position.
"pepRoleInformation": {
    "status": {
        "value": "wcStatus:ACTIVE", <-------------
        "valueDataType": "wcDataType:Q_CODE"
    },
    "pepRoleDetails": [
        {
            "id": "3321d09da597070b76c0d8ace4fcd794",
            "role": {
                "value": "wcPepRole:CAB_MINI",
                "valueDataType": "wcDataType:Q_CODE"
            },
            "level": {
                "value": "wcPEPRoleLevel:NATIONAL",
                "valueDataType": "wcDataType:Q_CODE"
            },
            "position": {
                "value": "wcPepPosition:MEMOE",
                "valueDataType": "wcDataType:Q_CODE"
            },
            "effectiveFrom": {
                "value": "2020-08",
                "status": {
                    "value": "wcStatus:REPORTED"
                },
            },
            "effectiveTo": {
                "value": "2025-06",
                "status": {
                    "value": "wcStatus:CONFIRMED"
                },
            },
            "status": {
                "value": "wcStatus:FORMER",
                "valueDataType": "wcDataType:Q_CODE"
            },
            "roleBiography": [
                {
                    "value": "Minister of Social Affairs of the Transitional Government",
                    "valueDataType": "wcDataType:STRING"
                }
            ],
            "locationInformation": {
                "locationDetails": [
                    {
                        "type": "wcLocationType:PEP_LOCATION",
                        "details": [
                            {
                                "role": "wcLocationRole:COUNTRY",
                                "status": {
                                    "value": "wcStatus:FORMER",
                                    "valueDataType": "wcDataType:Q_CODE"
                                },
                                "value": "wcCountry:GH",
                                "valueDataType": "wcDataType:Q_CODE"
                            }
                        ]

PEP STATUS​

ProductField or Value / Record Area
World-Check Data FilePEP STATUS
World-Check On Demandrecord.pepRoleInformation.status.value

The legacy PEP STATUS values are mapped to the status object within the pepRoleInformation record area in World-Check On Demand. Please see the example for PEP ROLES above.

SPECIAL INTEREST CATEGORIES​

ProductField or Value / Record Area
World-Check Data FileSPECIAL INTEREST CATEGORIES
World-Check On Demandrecord.categoryInformation.categories.categoryPath

Entries in the legacy SPECIAL INTEREST CATEGORIES are mapped to the new categorisation taxonomy in World-Check On Demand, specifically as Category 3 concepts. However, all these values are under the wcCat1:SPECIAL_INTEREST Category 1 concept.

A World-Check On Demand Category example showing multiple category paths, including Special Interest Categories.
"categoryInformation": {
    "categories": [
        {
            "categoryPath": "wcCat1:POST_CONVICTION/wcCat2:CRIME_OTHER",
            "id": "73f4d9ba9ec09f35ee811a3b11c04939",
            "isDefault": true
        },
        {
            "categoryPath": "wcCat1:SPECIAL_INTEREST/wcCat2:TRAF/wcCat3:TRAHU", <-------------
            "id": "9510941ff99af39a04a5b5e7418142c9"
        },
        {
            "categoryPath": "wcCat1:SPECIAL_INTEREST/wcCat2:HRIGV/wcCat3:HRIGHV", <-------------
            "id": "66eee9a973bc708a51c9d5704f8c9ac4"
        }
    ]
},
SPECIAL INTEREST CATEGORIES in World-Check Data FileCategory 3 in World-Check On DemandCategory 2 in World-Check On Demand
Absconder or FugitivewcCat3:ABFUwcCat2:ENFORCE
Abuse of OfficewcCat3:ABUOFwcCat2:CIV_CORP
Aiding and AbettingwcCat3:AIABwcCat2:OTHERCRIME
Aircraft Hijacking and Aviation CrimewcCat3:ACRIMwcCat2:VCRIM
Antitrust Violation or Unlawful CompetitionwcCat3:ANTRVwcCat2:OTHERCRIME
Arms and Ammunition PossessionwcCat3:UNGUN1wcCat2:OTHERCRIME
Arms and Ammunition TraffickingwcCat3:TRAGUwcCat2:TRAF
Arson and Destruction of PropertywcCat3:DEPROwcCat2:VCRIM
Breach of Fiduciary DutywcCat3:BRFIDwcCat2:CIV_CORP
Bribery and CorruptionwcCat3:CRRPT1wcCat2:FINANCIAL
Conspiracy or CollusionwcCat3:CNSPR1wcCat2:OTHERCRIME
Consumer Protection ViolationwcCat3:CONSPwcCat2:CIV_CORP
Control or Regulation ViolationwcCat3:COREVwcCat2:CIV_CORP
Counterfeiting or PiracywcCat3:FAKEDwcCat2:OTHERCRIME
Crimes Against the StatewcCat3:STCRIMwcCat2:OTHERCRIME
CybercrimewcCat3:HACK1wcCat2:INFOSEC
Data Privacy BreachwcCat3:DAPBRwcCat2:INFOSEC
Deported or ExiledwcCat3:DEPORTwcCat2:ENFORCE
Disciplinary ActionwcCat3:DACTwcCat2:ENFORCE
Disqualified or DebarredwcCat3:DISQwcCat2:ENFORCE
Dissolved CompanywcCat3:DISCOMwcCat2:ENFORCE
Energy CrimewcCat3:ENCRIMwcCat2:OTHERCRIME
Environmental CrimewcCat3:EVCRIMwcCat2:ENVIROMENT
Exploitation of ChildrenwcCat3:KIDEX1wcCat2:HRIGV
ExtortionwcCat3:XTRTNwcCat2:FINANCIAL
Financial Services WarningwcCat3:FINSWwcCat2:ENFORCE
Forced and Slave LabourwcCat3:SLAVE1wcCat2:HRIGV
Forgery and UtteringwcCat3:FRGRYwcCat2:OTHERCRIME
FraudwcCat3:DCPTN1wcCat2:FINANCIAL
Frozen and Seized AssetswcCat3:FRASwcCat2:ENFORCE
Hate CrimewcCat3:HCRIMwcCat2:HRIGV
Healthcare FraudwcCat3:HCFDwcCat2:FINANCIAL
Human Rights ViolationwcCat3:HRIGHVwcCat2:HRIGV
Human TraffickingwcCat3:TRAHUwcCat2:TRAF
Illegal ImmigrationwcCat3:ILLIM1wcCat2:OTHERCRIME
Illegal Possession or SalewcCat3:ILLCOwcCat2:OTHERCRIME
Illegal Restraint or KidnappingwcCat3:RESKIDwcCat2:VCRIM
Insider TradingwcCat3:INTRD1wcCat2:FINANCIAL
Insolvency, Liquidation or BankruptcywcCat3:INLIBKwcCat2:ENFORCE
IP Rights InfringementwcCat3:IPIN1wcCat2:INFOSEC
Labour Rights ViolationwcCat3:JOBVIwcCat2:HRIGV
Licence or Registration RevocationwcCat3:LICREwcCat2:ENFORCE
Money LaunderingwcCat3:MOLND1wcCat2:FINANCIAL
Narcotics TraffickingwcCat3:NARTRAwcCat2:TRAF
Obstruction of JusticewcCat3:OBSJUwcCat2:OTHERCRIME
Organized CrimewcCat3:OCRIM1wcCat2:OCRIM
Pharmaceutical TraffickingwcCat3:TRAPHAwcCat2:TRAF
Securities ViolationwcCat3:SECVIwcCat2:FINANCIAL
Sexual ExploitationwcCat3:SEXEXwcCat2:HRIGV
SmugglingwcCat3:SMGLNGwcCat2:TRAF
Tax and Customs ViolationwcCat3:TAXCUVwcCat2:FINANCIAL
Tender Violation and RestrictionswcCat3:TENVwcCat2:FINANCIAL
Terror RelatedwcCat3:TERRO1wcCat2:TERRO
Theft and EmbezzlementwcCat3:THFT1wcCat2:FINANCIAL
Trafficking in Stolen GoodswcCat3:TRAGDwcCat2:TRAF
Travel or Visa RestrictionwcCat3:TRRESwcCat2:SNCTN1
Unlawful Money LendingwcCat3:UNMOwcCat2:FINANCIAL
Violent CrimewcCat3:VCRIM1wcCat2:VCRIM
War CrimewcCat3:WRCRI1wcCat2:VCRIM
Wildlife CrimewcCat3:WICRIMwcCat2:ENVIROMENT
Illegal GamblingwcCat3:ILLGAwcCat2:OTHERCRIME
tip

Additional entries in World-Check On Demand may be added over time. Please refer to the Reference API content for the latest entries.

NATIVE CHARACTER NAMES (Native Character File)​

ProductField or Value / Record Area
World-Check Data (Native Character) FileNATIVE CHARACTER NAMES
World-Check On Demandrecord.nameInformation.nameDetails.details.value
An example of a Name Information entry with native characters.
"nameInformation": {
    "nameDetails": [
{
    "details": [
        {
            "role": "wcNameRole:STRING_NAME",
            "value": "约翰·威克", <-------------
            "valueDataType": "wcDataType:STRING"
        }
    ],
    "id": "f5b98672b63a804bb1667740b6b6508",
    "relations": [
        {
            "rel": "wcRelatedRel:IS_NON_LATIN_NAME", <-------------
            "value": "true",
            "valueDataType": "wcDataType:BOOLEAN"
        },
        {
            "rel": "wcRelatedRel:HAS_LANGUAGE", <-------------
            "value": "wcLanguage:ZH_CN",
            "valueDataType": "wcDataType:Q_CODE"
        },
        {
            "rel": "wcRelatedRel:HAS_WC_NAME_TYPE", <-------------
            "value": "wcNameType:AKA",
            "valueDataType": "wcDataType:Q_CODE"
        }
    ]
},

The names in NATIVE CHARACTER NAMES are mapped to entries in nameInformation, with some key differences:

  • equivalent entries in nameInformation for native character names will only have a string equivalent and are not broken into name components
  • nameDetails.isDefault = false or is not present in the nameDetails object
  • nameDetails.relations.value = wcNameType:AKA where rel = wcRelatedRel:HAS_WC_NAME_TYPE
  • nameDetails.relations.value = true where rel = wcRelatedRel:IS_NON_LATIN_NAME
  • nameDetails.relations.value = a concept within the wcLanguage scheme where rel = wcRelatedRel:HAS_LANGUAGE

DATE (Deleted Profiles File)​

ProductField or Value / Record Area
World-Check Data (Deleted Profiles) FileDATE
World-Check On Demandrecord.recordDateInformation.recordDateDetails.details.value
An example of a Record Date Information entry for a deleted record.
"recordDateInformation": {
    "recordDateDetails": [
        {
            "type": "wcRecordDateType:DELETION_DATE", <-------------
            "detail": {
                "role": "wcRecordDateRole:VALUE", 
                "value": "2025-08-27T06:29:08.217Z", <-------------
                "valueDataType": "wcDataType:DATETIME"
            }
        }
    ]
},

The Record Date Information section will also contain dates of record reactivation.

The date entries in the DATE field of the Deleted Profiles file are mapped to entries in recordDateInformation where:

  • recordDateDetails.type = wcRecordDateType:DELETION_DATE