Personator Identity:Request: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
Created page with "{{PersonatorWorldNav |InputOutputCollapse= }} {{CustomTOC}} A request consists of a protocol to make a call to the service, detailing desired elements. The minimum required..."
 
No edit summary
 
(15 intermediate revisions by the same user not shown)
Line 9: Line 9:


The web service supports REST and JSON protocols.
The web service supports REST and JSON protocols.
==URL==
{{URL-PersonatorWorld}}




Line 34: Line 38:
|-
|-
|National ID || nat || NationalID
|National ID || nat || NationalID
|-
|First name || first || FirstName
|-
|Last name || last || LastName
|-
|-
|Full name || full || FullName
|Full name || full || FullName
Line 44: Line 52:
|-
|-
|Date of birth || dob || DateOfBirth
|Date of birth || dob || DateOfBirth
|-
|Account Number || accountNumber || AccountNumber
|-
|-
|Address line 1 || a1 || AddressLine1
|Address line 1 || a1 || AddressLine1
Line 76: Line 86:
The following elements set the basic options for each request. These apply to the entire request, not the individual records.
The following elements set the basic options for each request. These apply to the entire request, not the individual records.


<h3 style="background-color:rgb(240,240,240);">Transmission Reference</h3>
<h3 class="h3grey">Transmission Reference</h3>
:''Optional.''
:''Optional.''


Line 90: Line 100:




<h3 style="background-color:rgb(240,240,240);">Customer ID</h3>
<h3 class="h3grey">Customer ID</h3>
:''Required.''
:''Required.''


Line 106: Line 116:




<h3 style="background-color:rgb(240,240,240);">Actions</h3>
<h3 class="h3grey">Actions</h3>
:''Required.''
:''Required.''


:This field determines what actions the service will perform on the input data. These actions are available:
:This field determines what actions the service will perform on the input data. These actions are available:


:*Check: Determines whether the data within a submitted record is valid, e.g. whether or not a given postal code contains the given city. It can also make limited corrections and appends to the data. Check looks at each data point separately.
:;*Check
::Determines whether the data within a submitted record is valid, e.g. whether or not a given postal code contains the given city. It can also make limited corrections and appends to the data. Check looks at each data point separately.


:;*Verify
:;*Verify
::After the data has been checked, identity verification is performed and result codes (KV*) are returned to indicate what pieces of input data have been matched against trusted referenced data.
::After the data has been checked, identity verification is performed and result codes (KV*) are returned to indicate what pieces of input data have been matched against trusted referenced data.
:;*Screen
::Screens the provided input against various government sanctions and watchlists and returns back a list of matches. For a list of used watchlists, see [[Personator Identity:Watchlists|Personator Identity Watchlists]].




For every request, a Check action is always performed on the input.
:For every request, a Check action is always performed on the input.


:{| class="alternate01"
:{| class="alternate01"
Line 128: Line 142:




<h3 style="background-color:rgb(240,240,240);">Address Options</h3>
<h3 class="h3grey">Address Options</h3>
:''Optional.''
:''Optional.''


Line 151: Line 165:




<h3 style="background-color:rgb(240,240,240);">Name Options</h3>
:<h4 style="border-bottom:1px solid black;">DeliveryLines</h4>
::This options allows you to specify if the Address Lines 1-8 should contain just the delivery address or the entire address.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''DeliveryLines'''||<code>Off</code>||'''''Default.''''' Address Lines 1-8 return the entire address.
|-
|<code>On</code>||Address Lines 1-8 return just the street address and dependent locality. It will not contain locality, administrative area, postal code, etc.
|}
 
 
:<h4 style="border-bottom:1px solid black;">LineSeparator</h4>
::This is the line separator used for the FormattedAddress result.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="7"|'''LineSeparator'''||<code>SEMICOLON</code>||'''''Default.''''' A semicolon (;).
|-
|<code>PIPE</code>||A pipe <nowiki>(|)</nowiki>.
|-
|<code>CR</code>||A carriage return.
|-
|<code>LF</code>||A line feed.
|-
|<code>CRLF</code>||A carriage return + line feed.
|-
|<code>TAB</code>||A tab.
|-
|<code>BR</code>||A line break.
|}
 
 
:<h4 style="border-bottom:1px solid black;">OutputScript</h4>
::This is the script type used for all applicable fields.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="3"|'''OutputScript'''||<code>NOCHANGE</code>||'''''Default.''''' Returns the same script that is sent in.
|-
|<code>LATN</code>||Returns in the Latin script.
|-
|<code>NATIVE</code>||Returns in the native script for the designated country.
|}
 
 
:<h4 style="border-bottom:1px solid black;">CountryOfOrigin</h4>
::This is used to determine whether or not to include the country name as the last line in FormattedAddress.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|'''CountryOfOrigin'''
|(Any valid ISO-3166-1 Alpha-2, ISO-3166-1 Alpha-3, or ISO-3166-1 Numeric code)
|
*If blank, invalid, or the same as the destination country, then the destination country is not appended to the end of the formatted address.
*If valid and different from the destination country, then the destination country is appended to the formatted address.
*US or US Territory:
:*If CountryOfOrigin and destination country being verified are both US or US Territories then the country will not be appended to FormattedAddress.
:*US Territories will have "United States of America" appended if the CountryOfOrigin is not a US Territory, but the CountryName and ISO codes will be that of the territory.
:*Canada is treated like any other non-US Territory.
|}
 
 
<h3 class="h3grey">Name Options</h3>
:''Optional.''
:''Optional.''


Line 174: Line 254:




<h3 style="background-color:rgb(240,240,240);">Email Options</h3>
:<h4 style="border-bottom:1px solid black;">CorrectFirstName</h4>
::This option enables or disables spelling correction of first names.
 
::A database of commonly misspelled first names is used to correct the values of the First Name properties.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''CorrectFirstName'''||<code>OFF</code>||'''''Default.''''' Preserve first name spellings; no correction allowed.
|-
|<code>ON</code>||Allows first name misspelling corrections.
|}
 
 
:<h4 style="border-bottom:1px solid black;">NameHint</h4>
::This option sets the most likely format of the FullName input string.
 
::This helps the service in cases where the order and formatting of the FullName input string are unclear.
 
::*Full or normal name order is: <Prefix> <First> <Middle>  <Last> <Suffix>.
::*Inverse name order is: <Last> <Suffix>, <Prefix> <First> <Middle>.
 
::Either the '''''Code''''' or '''''Name''''' listed below can be used to set the action.
 
::For example, <code>Options = NAMEHINT:4</code> and <code>Options = NAMEHINT:Varying</code> are equivalent settings.
 
 
::{|class="alternate01" cellspacing="0"
!Option Name!!Parameter Code!!Parameter Name!!Definition
|-
|rowspan="9"|'''NameHint'''||<code>1</code>||<code>DefinitelyFull</code>||Name will always be treated as normal name order regardless of formatting or punctuation.
|-
|<code>2</code>||<code>VeryLikelyFull</code>||Name will be treated as normal name order unless inverse order is clearly indicated by formatting or punctuation.
|-
|<code>3</code>||<code>ProbablyFull</code>||If necessary, statistical logic will be employed to determine name order, with a bias towards normal name order.
|-
|<code>4</code>||<code>Varying</code>||'''''Default.''''' If necessary, statistical logic will be employed to determine name order, with no bias toward either name order.
|-
|<code>5</code>||<code>ProbablyInverse</code>||If necessary, statistical logic will be employed to determine name order, with a bias toward inverse name order.
|-
|<code>6</code>||<code>VeryLikelyInverse</code>||Name will be treated as inverse name order unless normal order is clearly indicated by formatting or punctuation.
|-
|<code>7</code>||<code>DefinitelyInverse</code>||Name will always be treated as inverse name order, regardless of formatting or punctuation.
|-
|<code>8</code>||<code>MixedFirstName</code>||Name element is expected to only contain first names.
|-
|<code>9</code>||<code>MixedLastName</code>||Name element is expected to only contain last names.
|}
 
 
:<h4 style="border-bottom:1px solid black;">GenderPopulation</h4>
::This option sets the gender balance of the source data, predominantly male, predominantly female, or neutral.
 
::If you know that the majority of inputted names will be predominantly one gender, meaning that gender-neutral names will likely be of a particular gender, use this property to set the gender bias while genderizing names.
 
::Either the ‘Code’ or ‘Name’ listed below can be used to set the action.
 
::For example, <code>Options = GENDERPOPULATION:3</code> and <code>Options = GENDERPOPULATION:Female</code> are equivalent settings.
 
 
::{|class="alternate01" cellspacing="0"
!Option Name!!Parameter Code!!Parameter Name!!Definition
|-
|rowspan="3"|'''GenderPopulation'''||<code>1</code>||<code>Male</code>||Bias toward male.
|-
|<code>2</code>||<code>Mixed</code>||'''''Default.''''' No bias toward either gender.
|-
|<code>3</code>||<code>Female</code>||Bias toward female.
|}
 
 
:<h4 style="border-bottom:1px solid black;">GenderAggression</h4>
::This option sets how aggressively the service will attempt to genderize neutral first names.
 
::By default, a value of “N” will be assigned when attempting to genderize a first name that can easily be male or female, such as “Taylor,” “Chris,” or “Pat.”
 
::Using this property in conjunction with the GenderPopulation option, you can instruct the service on how much preference to give one gender over the other when assigning a gender to a normally neutral name.
 
::Either the ‘Code’ or ‘Name’ listed below can be used to set the action.
 
::For example, <code>Options = GENDERAGGRESSION:2</code> and <code>Options = GENDERAGGRESSION:Neutral</code> are equivalent settings.
 
 
::{|class="alternate01" cellspacing="0"
!Option Name!!Parameter Code!!Parameter Name!!Definition
|-
|rowspan="3"|'''GenderAggression'''||<code>1</code>||<code>Aggressive</code>||Aggressive name genderizing.
|-
|<code>2</code>||<code>Neutral</code>||'''''Default.''''' Neutral name genderizing.
|-
|<code>3</code>||<code>Conservative</code>||Conservative name genderizing.
|}
 
 
::The table below shows how the settings for Gender Aggression and Gender Population affect genderizing:
 
::{| cellspacing="0" class="genderTable"
|
|colspan="3" class="genderTableBlue"|Male
|
|colspan="3" class="genderTablePink"|Female
|-
!Aggression
|class="genderTableBlue"|Always [7]
|class="genderTableBlue"|Often [6]
|class="genderTableBlue"|Normally [5]
|Neutral [4]
|class="genderTablePink"|Normally [3]
|class="genderTablePink"|Often [2]
|class="genderTablePink"|Always [1]
|-
!colspan="8" class="genderTableGreen"|Conservative
|-
!style="text-align:left;"|Even
|class="genderTableBlue"|M
|class="genderTableBlue"|N
|class="genderTableBlue"|N
|N
|class="genderTablePink"|N
|class="genderTablePink"|N
|class="genderTablePink"|F
|-
!style="text-align:left;"|Male
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|N
|N
|class="genderTablePink"|N
|class="genderTablePink"|N
|class="genderTablePink"|F
|-
!style="text-align:left;"|Females
|class="genderTableBlue"|M
|class="genderTableBlue"|N
|class="genderTableBlue"|N
|N
|class="genderTablePink"|N
|class="genderTablePink"|F
|class="genderTablePink"|F
|-
!colspan="8" class="genderTableOrange"|Neutral
|-
!style="text-align:left;"|Even
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|N
|N
|class="genderTablePink"|N
|class="genderTablePink"|F
|class="genderTablePink"|F
|-
!style="text-align:left;"|Male
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|N
|class="genderTablePink"|N
|class="genderTablePink"|F
|class="genderTablePink"|F
|-
!style="text-align:left;"|Females
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|N
|N
|class="genderTablePink"|F
|class="genderTablePink"|F
|class="genderTablePink"|F
|-
!colspan="8" class="genderTableRed"|Aggressive
|-
!style="text-align:left;"|Even
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|N
|class="genderTablePink"|F
|class="genderTablePink"|F
|class="genderTablePink"|F
|-
!style="text-align:left;"|Male
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|M
|class="genderTablePink"|N
|class="genderTablePink"|F
|class="genderTablePink"|F
|-
!style="text-align:left;"|Females
|class="genderTableBlue"|M
|class="genderTableBlue"|M
|class="genderTableBlue"|N
|F
|class="genderTablePink"|F
|class="genderTablePink"|F
|class="genderTablePink"|F
|}
 
 
:<h4 style="border-bottom:1px solid black;">MiddleNameLogic</h4>
::This option controls how middle names are handled.
 
::Some names can be ambiguous with regards to the middle word of a full name. It may be a middle name or it may be the first part of a hyphenated last name, but the hyphen has been omitted for some reason.
 
::Normally, the service assumes that, in the absence of a hyphen, recognizable last names in the middle of a full name are treated as part of a hyphenated last name. “Mary O’Malley Kelly” is parsed into first name “Mary” and last name “O’Malley-Kelly.”
 
::On the other hand, “Colleen Marie Sullivan” is parsed into first name “Colleen,” middle name “Marie,” and last name “Sullivan.”
 
::Either the ‘Code’ or ‘Name’ listed below can be used to set the action.
 
::For example, <code>Options = MIDDLENAMELOGIC:0</code> and <code>Options = MIDDLENAMELOGIC:ParseLogic</code> are equivalent settings.
 
 
::{|class="alternate01" cellspacing="0"
!Option Name!!Parameter Code!!Parameter Name!!Definition
|-
|rowspan="3"|'''MiddleNameLogic'''||<code>0</code>||<code>ParseLogic</code>||'''''Default.''''' The service behaves as described above.
|-
|<code>1</code>||<code>HyphenatedLast</code>||The middle word is assumed to be part of the last name. “Matthew Edward Jones” is treated as “Matthew Edward-Jones.”
|-
|<code>2</code>||<code>MiddleName</code>||The middle word is assumed to be a middle name. for the name “Mary O’Malley Kelly,” O’Malley is assumed to be the middle name.
|}
 
::When a hyphen is present, the hyphenated word is always treated as the last name, regardless of content.
 
 
<h3 class="h3grey">Email Options</h3>
:''Optional.''
:''Optional.''


Line 197: Line 504:




<h3 style="background-color:rgb(240,240,240);">Phone Options</h3>
:<h4 style="border-bottom:1px solid black;">VerifyMailBox</h4>
::VerifyMailBox validates email mailbox.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''VerifyMailBox'''||<code>Express</code>||'''''Default.''''' Also known as fast mode. Quickly validates against database of known email addresses.
|-
|<code>Premium</code>||Also known as real time mode. Perform real time, live validation of email addresses.
|}
 
 
:<h4 style="border-bottom:1px solid black;">DomainCorrection</h4>
::DomainCorrection turns on fuzzy correction on suspected email domains typos.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''DomainCorrection'''||<code>On</code>||'''''Default.''''' Activates fuzzy email domain correction if the domain is a suspected typo.
|-
|<code>Off</code>||No email domain correction.
|}
 
 
:<h4 style="border-bottom:1px solid black;">TimeToWait</h4>
::TimeToWait allows you to select how long (in seconds) that you would like our web service to wait on a single email before it times out. Select a smaller number if time is of essence, or longer if you would prefer more accurate results.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|'''TimeToWait'''||<code># [5 - 45]</code>||'''''Default set to 25.''''' Select how long the web service will wait before it times out on an email.
|}
 
 
<h3 class="h3grey">Phone Options</h3>
:''Optional.''
:''Optional.''


Line 220: Line 561:




<h3 style="background-color:rgb(240,240,240);">Options</h3>
:<h4 style="border-bottom:1px solid black;">CallerID</h4>
::Returns the name or association linked to the phone number at the time of registration, if available.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''CallerID'''||<code>False</code>||'''''Default.''''' CallerID is turned off.
|-
|<code>True</code>||Adds the CallerID to the queried phone, if we found it to be valid.
|}
 
 
:<h4 style="border-bottom:1px solid black;">DefaultCallingCode</h4>
::DefaultCallingCode is used when the country could not be detected from the phone number or country input.
 
::A calling code is a sequence of digits often found after the leading ‘+’ and is unique to a country/region.
 
::By default, this value is blank. For more information on country calling codes, please see: https://en.wikipedia.org/wiki/List_of_country_calling_codes.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter
|-
|'''DefaultCallingCode'''||<code>Country Calling Code</code>
|}
 
 
:<h4 style="border-bottom:1px solid black;">TimeToWait</h4>
::Determines how long the service takes to query a phone number for Premium or CallerID, before it decides to time out.
 
::Time to wait in seconds. Minimum value is 1, maximum value is 30.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|'''TimeToWait'''||(Time in seconds)||'''''Default is 2.''''' Time to wait in seconds.
|}
 
 
:<h4 style="border-bottom:1px solid black;">VerifyPhone</h4>
::VerifyPhone sets the level of verification to be done on a phone check.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''VerifyPhone'''||<code>Express</code>||'''''Default.''''' Quickly validates against a database of known phone numbers.
|-
|<code>Premium</code>||Validates against a database of known phone numbers. If a number was last real-time validated more than 30 days ago, then a real-time check will be performed.
|}
 
 
<h3 class="h3grey">Options</h3>
:''Optional.''
:''Optional.''


:This is a string value containing other mscellaneous options related to the web service. There are no other options currently available. This is reserved for future use.
:This is a string value containing other mscellaneous options related to the web service.


:{| class="alternate01"
:{| class="alternate01"
Line 234: Line 625:




<h3 style="border-bottom:1px solid black;">National ID</h3>
:List options in the following format, with multiple options delimited with a ",".
 
:{| class="alternate01"
!Syntax
|-
|<code>''OptionName'':''Parameter'',''OptionName'':''Parameter''</code>
|}
 
 
:<h4 style="border-bottom:1px solid black;">Consent</h4>
::Option for data sources that require consent to be given – acknowledging that consent is given to allow the data to be verified by external data sources.
 
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="2"|'''Consent'''||<code>No</code>||'''''Default.''''' Indicates that no consent was given.
|-
|<code>Yes</code>||Indicates that consent was given.
|}
 
 
<h3 class="h3grey">Privacy</h3>
:''Optional.''
 
:This Option allows data elements to be redacted from the response. User can submit any combination of data elements to redact, or all elements. All result codes will be returned to the client will be returned to the user.
 
:{| class="alternate01"
!Protocol !! Syntax
|-
|JSON||<code>"Privacy":"'''''string'''''"</code>
|-
|REST||<code>&privacy = '''''string'''''</code>
|}
 
 
:List data elements to redact in the following format, with multiple elements delimited with a ",".
 
:{| class="alternate01"
!Syntax
|-
|<code>Privacy:value1,value2,value3</code>
|}
 
 
:<h4 style="border-bottom:1px solid black;">Privacy</h4>
::{| class="alternate01 sortable"
!Option Name !! Parameter !! Description
|-
|rowspan="6"|'''Privacy'''||<code>[None]</code>||'''''Default.''''' All data elements will be returned
|-
|<code>name</code>||Redact name fields.
|-
|<code>address</code>||Redact address fields.
|-
|<code>phone</code>||Redact phone fields.
|-
|<code>email</code>||Redact email fields.
|-
|<code>all</code>||Redact all fields.
|}
 
 
<h3 class="h3grey">National ID</h3>
:''Optional.''
:''Optional.''


Line 248: Line 701:




<h3 style="border-bottom:1px solid black;">Full Name</h3>
<h3 class="h3grey">First Name</h3>
:''Recommended.''
 
:The given (first) name.
 
:{| class="alternate01"
!Protocol !! Syntax
|-
|JSON||<code>"FirstName":"'''''string'''''"</code>
|-
|REST||<code>&first = '''''string'''''</code>
|}
 
 
<h3 class="h3grey">Last Name</h3>
:''Recommended.''
 
:The family (last name) or surname.
 
:{| class="alternate01"
!Protocol !! Syntax
|-
|JSON||<code>"LastName":"'''''string'''''"</code>
|-
|REST||<code>&last = '''''string'''''</code>
|}
 
 
<h3 class="h3grey">Full Name</h3>
:''Recommended.''
:''Recommended.''


:The full name to be genderized, standardized, and parsed.
:The full name to be genderized, standardized, and parsed.
:We will parse and check full names only if the first name and last name fields are left blank.


:{| class="alternate01"
:{| class="alternate01"
Line 262: Line 745:




<h3 style="border-bottom:1px solid black;">Company</h3>
<h3 class="h3grey">Company</h3>
:''Optional.''
:''Optional.''


Line 276: Line 759:




<h3 style="border-bottom:1px solid black;">Phone Number</h3>
<h3 class="h3grey">Phone Number</h3>
:''Optional.''
:''Optional.''


Line 290: Line 773:




<h3 style="border-bottom:1px solid black;">Email</h3>
<h3 class="h3grey">Email</h3>
:''Optional.''
:''Optional.''


Line 304: Line 787:




<h3 style="border-bottom:1px solid black;">Date of Birth</h3>
<h3 class="h3grey">Date of Birth</h3>
:''Optional.''
:''Optional.''


Line 318: Line 801:




<h3 style="border-bottom:1px solid black;">Address Line 1</h3>
<h3 class="h3grey">Account Number</h3>
:''Optional.''
 
:The input field for account number. This should contain an IBAN or SWIFT number.
 
:{| class="alternate01"
!Protocol !! Syntax
|-
|JSON||<code>"AccountNumber":"'''''string'''''"</code>
|-
|REST||<code>&accountNumber = '''''string'''''</code>
|}
 
 
<h3 class="h3grey">Address Line 1</h3>
:''Required.''
:''Required.''


Line 332: Line 829:




<h3 style="border-bottom:1px solid black;">Address Line 2</h3>
<h3 class="h3grey">Address Line 2</h3>
:''Required.''
:''Required.''


Line 346: Line 843:




<h3 style="border-bottom:1px solid black;">Address Line 3</h3>
<h3 class="h3grey">Address Line 3</h3>
:''Required.''
:''Required.''


Line 360: Line 857:




<h3 style="border-bottom:1px solid black;">Address Line 4</h3>
<h3 class="h3grey">Address Line 4</h3>
:''Required.''
:''Required.''


Line 374: Line 871:




<h3 style="border-bottom:1px solid black;">Address Line 5</h3>
<h3 class="h3grey">Address Line 5</h3>
:''Required.''
:''Required.''


Line 388: Line 885:




<h3 style="border-bottom:1px solid black;">Address Line 6</h3>
<h3 class="h3grey">Address Line 6</h3>
:''Required.''
:''Required.''


Line 402: Line 899:




<h3 style="border-bottom:1px solid black;">Address Line 7</h3>
<h3 class="h3grey">Address Line 7</h3>
:''Required.''
:''Required.''


Line 416: Line 913:




<h3 style="border-bottom:1px solid black;">Address Line 8</h3>
<h3 class="h3grey">Address Line 8</h3>
:''Required.''
:''Required.''


Line 430: Line 927:




<h3 style="background-color:rgb(240,240,240);">Locality</h3>
<h3 class="h3grey">Locality</h3>
:''Required.''
:''Required.''


Line 447: Line 944:




<h3 style="background-color:rgb(240,240,240);">Administrative Area</h3>
<h3 class="h3grey">Administrative Area</h3>
:''Required.''
:''Required.''


Line 464: Line 961:




<h3 style="background-color:rgb(240,240,240);">PostalCode</h3>
<h3 class="h3grey">PostalCode</h3>
:''Required.''
:''Required.''


Line 480: Line 977:




<h3 style="background-color:rgb(240,240,240);">Country</h3>
<h3 class="h3grey">Country</h3>
:''Required.''
:''Required.''


Line 494: Line 991:




<h3 style="border-bottom:1px solid black;">Country of Origin</h3>
<h3 class="h3grey">Country of Origin</h3>
:''Optional.''
:''Optional.''


Line 508: Line 1,005:




[[Category:Personator World]]
[[Category:Personator Identity]]
[[Category:Reference]]
[[Category:Reference]]

Latest revision as of 22:49, 15 April 2024

← Personator Identity

Personator Identity Navigation
Introduction
Licensing
Input/Output
Request Fields
Response Fields
Examples
REST JSON
POST JSON
Result Codes
Result Code Use
Personator Identity Result Codes
Sample Code



A request consists of a protocol to make a call to the service, detailing desired elements. The minimum required elements in a request are your Customer ID (License Key) and the fields listed as Required below.

The web service supports REST and JSON protocols.


URL

REST, JSON

Use URL
Secure https://globalpersonator.melissadata.net/v1/doContactVerify


Field Names

This is a list of the request field names and their protocol naming conventions.

Field Name REST JSON
Transmission Reference t TransmissionReference
Customer ID id CustomerID
Actions act Actions
Address options addrOpt AddressOptions
Name options nameOpt NameOptions
Email options emailOpt EmailOptions
Phone options phoneOpt PhoneOptions
Options opt Options
National ID nat NationalID
First name first FirstName
Last name last LastName
Full name full FullName
Company comp Company
Phone number phone PhoneNumber
Email email Email
Date of birth dob DateOfBirth
Account Number accountNumber AccountNumber
Address line 1 a1 AddressLine1
Address line 2 a2 AddressLine2
Address line 3 a3 AddressLine3
Address line 4 a4 AddressLine4
Address line 5 a5 AddressLine5
Address line 6 a6 AddressLine6
Address line 7 a7 AddressLine7
Address line 8 a8 AddressLine8
Locality loc Locality
Administrative area admarea AdministrativeArea
Postal code postal PostalCode
Country ctry Country
Country of origin ctryorg CountryOfOrigin


Request Elements

The following elements set the basic options for each request. These apply to the entire request, not the individual records.

Transmission Reference

Optional.
This is a string value that serves as a unique identifier for this set of records. It is returned as sent.
Protocol Syntax
JSON "TransmissionReference":"string"
REST ?t = string


Customer ID

Required.
This is a string value containing the License Key issued to the customer by Melissa Data for the web service.
If this element is absent, the web service will return an error. To receive a License Key, please contact your Melissa Data sales representative at 1-800-MELISSA.
Protocol Syntax
JSON "CustomerID":"string"
REST &id = string


Actions

Required.
This field determines what actions the service will perform on the input data. These actions are available:
  • Check
Determines whether the data within a submitted record is valid, e.g. whether or not a given postal code contains the given city. It can also make limited corrections and appends to the data. Check looks at each data point separately.
  • Verify
After the data has been checked, identity verification is performed and result codes (KV*) are returned to indicate what pieces of input data have been matched against trusted referenced data.
  • Screen
Screens the provided input against various government sanctions and watchlists and returns back a list of matches. For a list of used watchlists, see Personator Identity Watchlists.


For every request, a Check action is always performed on the input.
Protocol Syntax
JSON "Actions":"string"
REST &act = string


Address Options

Optional.
This is a string value containing the address options set by the user when the address is being validated during the Check action.
Protocol Syntax
JSON "AddressOptions":"string"
REST &addrOpt = string


List options in the following format, with multiple options delimited with a ",".
Syntax
OptionName:Parameter,OptionName:Parameter


DeliveryLines

This options allows you to specify if the Address Lines 1-8 should contain just the delivery address or the entire address.
Option Name Parameter Description
DeliveryLines Off Default. Address Lines 1-8 return the entire address.
On Address Lines 1-8 return just the street address and dependent locality. It will not contain locality, administrative area, postal code, etc.


LineSeparator

This is the line separator used for the FormattedAddress result.
Option Name Parameter Description
LineSeparator SEMICOLON Default. A semicolon (;).
PIPE A pipe (|).
CR A carriage return.
LF A line feed.
CRLF A carriage return + line feed.
TAB A tab.
BR A line break.


OutputScript

This is the script type used for all applicable fields.
Option Name Parameter Description
OutputScript NOCHANGE Default. Returns the same script that is sent in.
LATN Returns in the Latin script.
NATIVE Returns in the native script for the designated country.


CountryOfOrigin

This is used to determine whether or not to include the country name as the last line in FormattedAddress.
Option Name Parameter Description
CountryOfOrigin (Any valid ISO-3166-1 Alpha-2, ISO-3166-1 Alpha-3, or ISO-3166-1 Numeric code)
  • If blank, invalid, or the same as the destination country, then the destination country is not appended to the end of the formatted address.
  • If valid and different from the destination country, then the destination country is appended to the formatted address.
  • US or US Territory:
  • If CountryOfOrigin and destination country being verified are both US or US Territories then the country will not be appended to FormattedAddress.
  • US Territories will have "United States of America" appended if the CountryOfOrigin is not a US Territory, but the CountryName and ISO codes will be that of the territory.
  • Canada is treated like any other non-US Territory.


Name Options

Optional.
This is a string value containing the name options set by the user when the name is being validated during the Check action.
Protocol Syntax
JSON "NameOptions":"string"
REST &nameOpt = string


List options in the following format, with multiple options delimited with a ",".
Syntax
OptionName:Parameter,OptionName:Parameter


CorrectFirstName

This option enables or disables spelling correction of first names.
A database of commonly misspelled first names is used to correct the values of the First Name properties.
Option Name Parameter Description
CorrectFirstName OFF Default. Preserve first name spellings; no correction allowed.
ON Allows first name misspelling corrections.


NameHint

This option sets the most likely format of the FullName input string.
This helps the service in cases where the order and formatting of the FullName input string are unclear.
  • Full or normal name order is: <Prefix> <First> <Middle> <Last> <Suffix>.
  • Inverse name order is: <Last> <Suffix>, <Prefix> <First> <Middle>.
Either the Code or Name listed below can be used to set the action.
For example, Options = NAMEHINT:4 and Options = NAMEHINT:Varying are equivalent settings.


Option Name Parameter Code Parameter Name Definition
NameHint 1 DefinitelyFull Name will always be treated as normal name order regardless of formatting or punctuation.
2 VeryLikelyFull Name will be treated as normal name order unless inverse order is clearly indicated by formatting or punctuation.
3 ProbablyFull If necessary, statistical logic will be employed to determine name order, with a bias towards normal name order.
4 Varying Default. If necessary, statistical logic will be employed to determine name order, with no bias toward either name order.
5 ProbablyInverse If necessary, statistical logic will be employed to determine name order, with a bias toward inverse name order.
6 VeryLikelyInverse Name will be treated as inverse name order unless normal order is clearly indicated by formatting or punctuation.
7 DefinitelyInverse Name will always be treated as inverse name order, regardless of formatting or punctuation.
8 MixedFirstName Name element is expected to only contain first names.
9 MixedLastName Name element is expected to only contain last names.


GenderPopulation

This option sets the gender balance of the source data, predominantly male, predominantly female, or neutral.
If you know that the majority of inputted names will be predominantly one gender, meaning that gender-neutral names will likely be of a particular gender, use this property to set the gender bias while genderizing names.
Either the ‘Code’ or ‘Name’ listed below can be used to set the action.
For example, Options = GENDERPOPULATION:3 and Options = GENDERPOPULATION:Female are equivalent settings.


Option Name Parameter Code Parameter Name Definition
GenderPopulation 1 Male Bias toward male.
2 Mixed Default. No bias toward either gender.
3 Female Bias toward female.


GenderAggression

This option sets how aggressively the service will attempt to genderize neutral first names.
By default, a value of “N” will be assigned when attempting to genderize a first name that can easily be male or female, such as “Taylor,” “Chris,” or “Pat.”
Using this property in conjunction with the GenderPopulation option, you can instruct the service on how much preference to give one gender over the other when assigning a gender to a normally neutral name.
Either the ‘Code’ or ‘Name’ listed below can be used to set the action.
For example, Options = GENDERAGGRESSION:2 and Options = GENDERAGGRESSION:Neutral are equivalent settings.


Option Name Parameter Code Parameter Name Definition
GenderAggression 1 Aggressive Aggressive name genderizing.
2 Neutral Default. Neutral name genderizing.
3 Conservative Conservative name genderizing.


The table below shows how the settings for Gender Aggression and Gender Population affect genderizing:
Male Female
Aggression Always [7] Often [6] Normally [5] Neutral [4] Normally [3] Often [2] Always [1]
Conservative
Even M N N N N N F
Male M M N N N N F
Females M N N N N F F
Neutral
Even M M N N N F F
Male M M M N N F F
Females M M N N F F F
Aggressive
Even M M M N F F F
Male M M M M N F F
Females M M N F F F F


MiddleNameLogic

This option controls how middle names are handled.
Some names can be ambiguous with regards to the middle word of a full name. It may be a middle name or it may be the first part of a hyphenated last name, but the hyphen has been omitted for some reason.
Normally, the service assumes that, in the absence of a hyphen, recognizable last names in the middle of a full name are treated as part of a hyphenated last name. “Mary O’Malley Kelly” is parsed into first name “Mary” and last name “O’Malley-Kelly.”
On the other hand, “Colleen Marie Sullivan” is parsed into first name “Colleen,” middle name “Marie,” and last name “Sullivan.”
Either the ‘Code’ or ‘Name’ listed below can be used to set the action.
For example, Options = MIDDLENAMELOGIC:0 and Options = MIDDLENAMELOGIC:ParseLogic are equivalent settings.


Option Name Parameter Code Parameter Name Definition
MiddleNameLogic 0 ParseLogic Default. The service behaves as described above.
1 HyphenatedLast The middle word is assumed to be part of the last name. “Matthew Edward Jones” is treated as “Matthew Edward-Jones.”
2 MiddleName The middle word is assumed to be a middle name. for the name “Mary O’Malley Kelly,” O’Malley is assumed to be the middle name.
When a hyphen is present, the hyphenated word is always treated as the last name, regardless of content.


Email Options

Optional.
This is a string value containing the email options set by the user when the email is being validated during the Check action.
Protocol Syntax
JSON "EmailOptions":"string"
REST &emailOpt = string


List options in the following format, with multiple options delimited with a ",".
Syntax
OptionName:Parameter,OptionName:Parameter


VerifyMailBox

VerifyMailBox validates email mailbox.
Option Name Parameter Description
VerifyMailBox Express Default. Also known as fast mode. Quickly validates against database of known email addresses.
Premium Also known as real time mode. Perform real time, live validation of email addresses.


DomainCorrection

DomainCorrection turns on fuzzy correction on suspected email domains typos.
Option Name Parameter Description
DomainCorrection On Default. Activates fuzzy email domain correction if the domain is a suspected typo.
Off No email domain correction.


TimeToWait

TimeToWait allows you to select how long (in seconds) that you would like our web service to wait on a single email before it times out. Select a smaller number if time is of essence, or longer if you would prefer more accurate results.
Option Name Parameter Description
TimeToWait # [5 - 45] Default set to 25. Select how long the web service will wait before it times out on an email.


Phone Options

Optional.
This is a string value containing the phone options set by the user when the phone is being validated during the Check action.
Protocol Syntax
JSON "PhoneOptions":"string"
REST &phoneOpt = string


List options in the following format, with multiple options delimited with a ",".
Syntax
OptionName:Parameter,OptionName:Parameter


CallerID

Returns the name or association linked to the phone number at the time of registration, if available.
Option Name Parameter Description
CallerID False Default. CallerID is turned off.
True Adds the CallerID to the queried phone, if we found it to be valid.


DefaultCallingCode

DefaultCallingCode is used when the country could not be detected from the phone number or country input.
A calling code is a sequence of digits often found after the leading ‘+’ and is unique to a country/region.
By default, this value is blank. For more information on country calling codes, please see: https://en.wikipedia.org/wiki/List_of_country_calling_codes.
Option Name Parameter
DefaultCallingCode Country Calling Code


TimeToWait

Determines how long the service takes to query a phone number for Premium or CallerID, before it decides to time out.
Time to wait in seconds. Minimum value is 1, maximum value is 30.
Option Name Parameter Description
TimeToWait (Time in seconds) Default is 2. Time to wait in seconds.


VerifyPhone

VerifyPhone sets the level of verification to be done on a phone check.
Option Name Parameter Description
VerifyPhone Express Default. Quickly validates against a database of known phone numbers.
Premium Validates against a database of known phone numbers. If a number was last real-time validated more than 30 days ago, then a real-time check will be performed.


Options

Optional.
This is a string value containing other mscellaneous options related to the web service.
Protocol Syntax
JSON "Options":"string"
REST &opt = string


List options in the following format, with multiple options delimited with a ",".
Syntax
OptionName:Parameter,OptionName:Parameter


Consent

Option for data sources that require consent to be given – acknowledging that consent is given to allow the data to be verified by external data sources.
Option Name Parameter Description
Consent No Default. Indicates that no consent was given.
Yes Indicates that consent was given.


Privacy

Optional.
This Option allows data elements to be redacted from the response. User can submit any combination of data elements to redact, or all elements. All result codes will be returned to the client will be returned to the user.
Protocol Syntax
JSON "Privacy":"string"
REST &privacy = string


List data elements to redact in the following format, with multiple elements delimited with a ",".
Syntax
Privacy:value1,value2,value3


Privacy

Option Name Parameter Description
Privacy [None] Default. All data elements will be returned
name Redact name fields.
address Redact address fields.
phone Redact phone fields.
email Redact email fields.
all Redact all fields.


National ID

Optional.
A string containing the national ID specific to the country. (e.g. in the US the Social Security Number)
Protocol Syntax
JSON "NationalID":"string"
REST &nat = string


First Name

Recommended.
The given (first) name.
Protocol Syntax
JSON "FirstName":"string"
REST &first = string


Last Name

Recommended.
The family (last name) or surname.
Protocol Syntax
JSON "LastName":"string"
REST &last = string


Full Name

Recommended.
The full name to be genderized, standardized, and parsed.
We will parse and check full names only if the first name and last name fields are left blank.
Protocol Syntax
JSON "FullName":"string"
REST &full = string


Company

Optional.
The company/organization name to be standardized.
Protocol Syntax
JSON "Company":"string"
REST &comp = string


Phone Number

Optional.
The phone number to be verified.
Protocol Syntax
JSON "PhoneNumber":"string"
REST &phone = string


Email

Optional.
The email address to be verified.
Protocol Syntax
JSON "Email":"string"
REST &email = string


Date of Birth

Optional.
The date of birth to be verified. The expected input format is YYYYMMDD.
Protocol Syntax
JSON "DateOfBirth":"string"
REST &dob = string


Account Number

Optional.
The input field for account number. This should contain an IBAN or SWIFT number.
Protocol Syntax
JSON "AccountNumber":"string"
REST &accountNumber = string


Address Line 1

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine1":"string"
REST &a1 = string


Address Line 2

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine2":"string"
REST &a2 = string


Address Line 3

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine3":"string"
REST &a3 = string


Address Line 4

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine4":"string"
REST &a4 = string


Address Line 5

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine5":"string"
REST &a5 = string


Address Line 6

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine6":"string"
REST &a6 = string


Address Line 7

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine7":"string"
REST &a7 = string


Address Line 8

Required.
The input field for the address. This should contain the delivery address information (house number, thoroughfare, building, suite, etc.) but should not contain locality information (locality, administrative area, postal code, etc.) which have their own inputs.
Protocol Syntax
JSON "AddressLine8":"string"
REST &a8 = string


Locality

Required.
The most common population center data element.
US Term: City
Canada Term: Municipality
Protocol Syntax
JSON "Locality":"string"
REST &loc = string


Administrative Area

Required.
The most common geographic data element.
US Term: State
Canada Term: Province
Protocol Syntax
JSON "AdministrativeArea":"string"
REST &admarea = string


PostalCode

Required.
The complete postal code for a particular delivery point.
If all three elements are provided and the PostalCode is incorrect, it can be corrected from the data on the Locality and AdministrativeArea.
Protocol Syntax
JSON "PostalCode":"string"
REST &postal = string


Country

Required.
The country name, abbreviation, or code.
Protocol Syntax
JSON "Country":"string"
REST &ctry = string


Country of Origin

Optional.
This is used to determine whether or not to include the country name as the last line in the FormattedAddress field.
Protocol Syntax
JSON "CountryOfOrigin":"string"
REST &ctryOrg = string