® ®

LexisNexis Accurint
QUICK REFERENCE GUIDE

Supplemental Web Service Interface Guide

BIS123-EN_US — 2 May 2023

CONFIDENTIAL
 CONFIDENTIAL

The recipient of this material (hereinafter “the Material”) acknowledges that it contains confidential
and proprietary data the disclosure to, or use of which by, third parties will be damaging to LexisNexis
Risk Solutions and its affiliated companies (hereinafter “LexisNexis Risk Solutions”). Therefore, recipient
agrees to hold the Material in strictest confidence, not to make use of it other than for the purpose for
which it is being provided, to release it only to employees requiring such information, and not to release
or disclose it to any other party. Upon request, recipient will return the Material together with all copies
and modifications, if any, to LexisNexis Risk Solutions.

LexisNexis Risk Solutions shall not be liable for technical or editorial errors or omissions contained
herein. The information in this publication is subject to change without notice and is provided “as-is”
without a warranty of any kind. Nothing herein should be construed as constituting a warranty, as any
applicable warranty is exclusively contained in your signed agreement with LexisNexis Risk Solutions.

All names, addresses, birth dates or other identifying information in the text, or on the sample reports
and screens shown in this document, are of fictitious persons and entities and have been created for
illustrative purposes only. Any similarity to the name of any real person, school, business, other entity,
address, date of birth, or other identifying information is purely coincidental.

LexisNexis and the Knowledge Burst logo are registered trademarks of RELX Inc. Accurint is a registered
trademark of LexisNexis Risk Data Management Inc. Other products and services may be trademarks or
registered trademarks of their respective companies.

© 2023 LexisNexis Risk Solutions

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 2

 CONFIDENTIAL

Co n t ent s
Introduction to Accurint Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
SOAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
REST Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
TLS Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
XML Integration Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Development Integration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Production Integration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Request Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Failover and DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Programming Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 3

 CONFIDENTIAL

I nt r o du ct i on to A cc urint Web Services

Accurint® makes your search easier by providing instant access to billions of linked records.

The Accurint proprietary data-linking technology returns search results in seconds. Accurint web services
allow you to find the information you are looking for using system-to-system processing by means of the
industry-standard SOAP (Simple Object Access Protocol).

Accurint functions have been tailored to fit the needs of major industries and can help you complete the
following tasks:

• Find people, businesses, and assets

• Obtain deep background information
• Uncover bankruptcies and criminal histories

This quick reference guide provides brief instructions for the Accurint functions. For detailed information
about the Accurint functions, see the LexisNexis® Accurint Web Service Interface Guide for Asset, Court,
and License Functions, the LexisNexis® Accurint Web Service Interface Guide for Business Functions, and
the LexisNexis® Accurint Web Service Interface Guide for People and Phone Functions.

Technical Support
During development, your LexisNexis® Risk Solutions XML consultant is your primary contact for
questions. After release into production, the LexisNexis Risk Solutions Production Support team is your
primary contact for questions.

For integration support and pre-production support, contact your XML consultant.

For production support and to add IP addresses to the allow list, use the following contact information:

• AccurintWebServices@lexisnexisrisk.com
• 888.270.2836

For many customers, live support is available all day, every day. For certain customers, after U.S. business
hours, please leave a message, and a production support representative will return your call.

For other questions or concerns, contact your account representative.

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 4

 CONFIDENTIAL

SOAP
You can communicate with LexisNexis Risk Solutions web services using the SOAP messaging standard.

There are many third-party tools and libraries that are available to simplify your SOAP client
development process. LexisNexis Risk Solutions can provide a WSDL (Web Services Description
Language) document that describes the web service and its messaging formats. Many SOAP tools can
use a WSDL document to generate source code, to set the message parameters, and to call into the
service.

The WSDL and XSD (XML Schema Definition) descriptions for Accurint web service functions are available
using a URL from the following list:

The URL must contain the desired version number. This is shown in the examples as ver_=n.nn&.
Use the actual version number in place of the n.nn. The WSDL and XSD version numbers are not
the same as the Accurint function version numbers. Contact the XML support team to get the
appropriate WSDL and XSD version numbers. For contact information, see "Technical Support" on
page 4.

Accurint Functions (replace [Function] with your specific function name)

https://wsonline.seisint.com/WsAccurint/[Function]?ver_=n.nn&wsdl

https://wsonline.seisint.com/WsAccurint/[Function]?ver_=n.nn&xsd

EchoTest
https://wsonline.seisint.com/WsAccurint/EchoTest?ver_=n.nn&wsdl

https://wsonline.seisint.com/WsAccurint/EchoTest?ver_=n.nn&xsd

You can also access the following site to test and interact with the functions:

https://wsonline.seisint.com/WsAccurint

REST Interface
LexisNexis Risk Solutions web services support the standard REST (representational state transfer)
interface.

The REST architecture uses name and value pairs to allow parameter passing. LexisNexis Risk Solutions
web services support two REST syntaxes: JSON (JavaScript object notation) and URI (Uniform Resource
Identifier).

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 5

 CONFIDENTIAL

The site https://wsonline.seisint.com/WsAccurint offers a Link to This Form option, which generates the
URI for you. Remove the “form&” parameter from the URI string that generates from the Link to This
Form option to submit the request. In the link that is generated using Link to This Form, the “.” that
precedes parent elements, such as “.User”, is optional. This site also offers a JSON test option at the
bottom of the page.

For URI, JSON, and SOAP examples, see the LexisNexis® Accurint Web Service Interface Guide for
Asset, Court, and License Functions, the LexisNexis® Accurint Web Service Interface Guide for Business
Functions, and the LexisNexis® Accurint Web Service Interface Guide for People and Phone Functions.

TLS Protocol
The TLS (transport layer security) protocol is designed to protect the security of web communications. To
provide the highest level of security, LexisNexis Risk Solutions requires that you use TLS version 1.2.

The following applications are compatible with the TLS 1.2 protocol:

• OpenSSL version 1.01 or later

• Java version 8 or later
You can configure Java version 7 to use the TLS 1.2 protocol.
• Microsoft .NET Framework version 4.6 or later
You can configure .NET Framework version 4.5 to use the TLS 1.2 protocol.
• Apache version 2.2.23 or later

Cr e de nt i al s
Your LexisNexis Risk Solutions XML consultant provides the XML on-boarding information and your XML
credentials. To prevent potential errors, you are issued two sets of user ID and password credentials.

X M L In t eg ra tion Checklist
There are tasks that you must complete as part of your XML implementation.

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 6

 CONFIDENTIAL

Development Integration Tasks

A list of tasks is provided that you must complete as part of your development implementation.

The following list is not a comprehensive list of development integration tasks, but the checklist is
designed to help ensure that you consider several critical elements with your development integration.

Download the WSDL files for the functions that you are coding. The latest version number for each
function is in the WSDL file. You must submit this version number in each request.
Provide your account number and all of your internet-facing IP addresses to LexisNexis Risk Solutions
XML Production Support so that the addresses can be added to an allow list for your account. (see
"Technical Support" on page 4).
Set up your firewall to allow access to the following IP address ranges:
• Subnet IPv4 – 209.243.48.0/20
• Subnet IPv4 – 69.84.176.0/20
• Subnet IPv4 – 198.62.62.0/23
• Subnet IPv4 – 69.84.182.0/23
• Subnet IPv6 – 2620:100:403e::/47
Provide your target release date to your LexisNexis Risk Solutions XML consultant.
Submit an echo test to verify that your authentication code is valid. For details about the EchoTest
function, see the LexisNexis® Accurint Web Service Interface Guide for Asset, Court, and License
Functions, the LexisNexis® Accurint Web Service Interface Guide for Business Functions, and the
LexisNexis® Accurint Web Service Interface Guide for People and Phone Functions.
• LexisNexis Risk Solutions recommends that you submit an echo test before you code to any
function. An echo test helps ensure that your authentication code works and that you can send a
basic SOAP request and receive a SOAP response.
• There is no cost to access the EchoTest function in LexisNexis Risk Solutions development web
services or LexisNexis Risk Solutions production web services.
Code to handle a SOAP fault. All status codes and error messages are passed through a 500 SOAP
fault. For details about the codes and messages that can help you resolve errors, see the LexisNexis®
Accurint Web Service Interface Guide for Asset, Court, and License Functions, the LexisNexis® Accurint
Web Service Interface Guide for Business Functions, and the LexisNexis® Accurint Web Service
Interface Guide for People and Phone Functions.
Code to accommodate failover to a secondary site (see "Failover and DNS" on page 10).
Use your development credentials to send a test transaction from your development server to the
LexisNexis Risk Solutions development server (see "Testing" on page 9).
• Submit the latest version number for the function in each request.
• Submit a value in the GLBPurpose element and the DLPurpose element for every transaction.
Use your development credentials to send a test transaction from your development server to the
LexisNexis Risk Solutions secondary site.
Contact your LexisNexis Risk Solutions XML consultant to review your test transactions.

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 7

 CONFIDENTIAL

Production Integration Tasks

A list of tasks is provided that you must complete as part of your production implementation.

The following list is not a comprehensive list of production integration tasks, but the checklist is designed
to help ensure that you consider several critical elements with your production integration.

Notify your LexisNexis Risk Solutions XML consultant and test your production credentials at least
two weeks before you deploy to production.
Use your production credentials to send a transaction from your production server to the LexisNexis
Risk Solutions production server.
Use your production credentials to send a test transaction from your production server to the
LexisNexis Risk Solutions secondary site.
Contact your LexisNexis Risk Solutions XML consultant to review your test transactions.

A u t h e n ti c ation
LexisNexis Risk Solutions web services support Basic HTTP authentication through HTTPS. SOAP Security
(through SOAP security header) is also supported.

Do not use both of these authentication methods in the same SOAP request. If your XML user name or
password is incorrect or if your IP address is not on the allow list, then the following error is returned:
401 Unauthorized.

Send your account credentials (user name and password) in the header of your request using Basic HTTP
authentication.

For codes samples that show how to send your credentials, see the LexisNexis® Accurint Web Service
Interface Guide for Asset, Court, and License Functions, the LexisNexis® Accurint Web Service Interface
Guide for Business Functions, and the LexisNexis® Accurint Web Service Interface Guide for People and
Phone Functions.

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 8

 CONFIDENTIAL

R eq u es t Elements
There are request requirements that you must consider as you create code to interact with LexisNexis
Risk Solutions web services.
Submit all of the required input elements. For specific input requirements, see the LexisNexis®
Accurint Web Service Interface Guide for Asset, Court, and License Functions, the LexisNexis® Accurint
Web Service Interface Guide for Business Functions, and the LexisNexis® Accurint Web Service
Interface Guide for People and Phone Functions.
Submit a value in the GLBPurpose element and the DLPurpose element for every transaction. If
you do not submit a valid value in these elements, then LexisNexis Risk Solutions uses the default
value 0 (No Permissible Purpose). For a list of permissible purpose values and their descriptions,
see the LexisNexis® Accurint Web Service Interface Guide for Asset, Court, and License Functions, the
LexisNexis® Accurint Web Service Interface Guide for Business Functions, and the LexisNexis® Accurint
Web Service Interface Guide for People and Phone Functions.
If you are a reseller, then you must submit all of the input elements in the EndUser structure in each
request.
Submit all SSN elements without hyphens (for example, 123004567).
Submit all phone numbers without hyphens, parenthesis, or periods (for example, 4065551234).
Submit all U.S. ZIP Codes in the Zip5 or Zip elements. Submit only international postal codes in the
PostalCode element.
If you need to send a unique transaction identifier from your database or application in your SOAP
request, then submit the ReferenceCode and QueryId elements. QueryId is not returned in the
response. For retrieval purposes, if you request for LexisNexis® to retrieve a transaction from the log
files, then you must provide a unique input element to identify the transaction. You can also provide
the TransactionID value that is returned in every response.
Submit a value in all of the Boolean input elements (for example, UseNicknames or UsePhonetics)
to help ensure that your application is not affected if the LexisNexis Risk Solutions default value
changes. If you do not want to use a Boolean option, then submit a value of 0.
If you use .NET Framework as your SOAP Toolkit, then Microsoft adds a “Specified” tag
to some of the LexisNexis Risk Solutions Boolean elements. You must send both versions
of the Boolean element. For example, if the LexisNexis Risk Solutions WSDL contains
the Boolean element <IncludeNicknames>, you must send both <IncludeNicknames> and
<IncludeNicknamesSpecified> in the SOAP request to LexisNexis Risk Solutions web services.

T e s t in g
LexisNexis Risk Solutions provides a test environment that provides options for testing. Your LexisNexis
Risk Solutions XML consultant provides your XML credentials for the test environment.

The test environment is located at the following website:

https://wsonline.seisint.com/Demo/WsAccurint/[Function]?ver_=n.nn

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 9

 CONFIDENTIAL

Use the actual version number in place of the n.nn. Replace [Function] with your specific function
name. The credentials that you use for authentication determine whether you access the test
environment or the production environment. Authenticate your access using your development
credentials. Development credentials always contain the letters DEV in the user ID (for example,
abcDEVxml).

Test seed cases are fictitious entities that are provided by LexisNexis Risk Solutions web services to
help you develop and test the XML interface. Test seed cases can be used to test connectivity, field
mapping, and various scoring and risk indicator scenarios free of charge. Your LexisNexis Risk Solutions
XML consultant sends you a Microsoft Excel spreadsheet that contains test seed data.

For details about the test environment, see the LexisNexis® Accurint Web Service Interface Guide for
Asset, Court, and License Functions, the LexisNexis® Accurint Web Service Interface Guide for Business
Functions, and the LexisNexis® Accurint Web Service Interface Guide for People and Phone Functions.

F a i lo ve r and DNS
Your application must follow failover and DNS (domain name system) guidelines.

The IP address that is associated with wsonline.seisint.com is subject to change without notice. In
particular, the IP address can change if LexisNexis Risk Solutions finds that it is necessary to fail over to
an alternate site. This can occur if there is a problem or programmed maintenance.

LexisNexis Risk Solutions maintains a standby, secondary data center that connects to a different internet
carrier. For failover and emergency purposes, set your DNS cache for all methods to very low (<=2
seconds). Set your TTL (time to live) to <=2.

A certificate warning may be returned if you directly access the secondary site. You can ignore this
warning. The secondary site is designed to redirect the primary URL to the query method.

If you manually fail over to the secondary site, then you should notify LexisNexis Risk Solutions Customer
Support so that LexisNexis Risk Solutions does not make changes that could unknowingly affect your
service.

If there is a TCP connection establishment failure or transaction timeout, then you must perform the
following steps:

1. Wait for a few seconds.

2. Resolve the DNS name again. LexisNexis Risk Solutions may have changed the external DNS names to
point to the secondary site in a failover process.
3. Retry the connection and transaction.

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 10

 CONFIDENTIAL

To help ensure the correct operation of your application, periodically perform a DNS lookup for
wsonline.seisint.com. If your application is unable to connect to wsonline.seisint.com, the
application should force a resolution of the wsonline.seisint.com IP address. If your organization
uses a proxy server, then add the URL to the proxy allow list.

In addition, make sure that your firewall allows outgoing TCP connections to port 443 to the following
range of IP addresses:

• Subnet IPv4 – 198.62.62.0/23

• Subnet IPv4 – 69.84.182.0/23
• Subnet IPv6 – 2620:100:403e::/47

If your application follows these rules, then failover to an alternate site should be transparent.

P r o g ram mi ng No tes
LexisNexis Risk Solutions provides programming notes that you should consider as you create code to
interact with LexisNexis Risk Solutions systems.

If you use .NET Framework as your SOAP Toolkit, and you have any of the following issues, then add a
web reference but direct the address to the local file instead of the URL to resolve:

• You have an issue consuming the WSDL.

• You have an issue when you generate your classes.
• The following error is returned:
Unable to cast COM object of type 'System.__ComObject'
• The following error is returned:
SOAP-ERROR: Parsing WSDL: Couldn't load from https://wsonline.seisint.com/
WsAccurint/[Function]?ver_=n.nn&wsdl' : failed to load external entity https://
wsonline.seisint.com/WsAccurint/[Function]?ver_=n.nn&wsdl

If you use Apache Axis as your SOAP Toolkit, there is a bug in the Axis code generation tool regarding its
use of the SOAP-reserved name TypeDesc. To work around this issue, use the parameter -H when you
generate the code. If you use this parameter, then the metadata is generated separately, and it avoids
the name collision for TypeDesc.

Do not program to the reason code descriptions. If you program to the descriptions, then any description
changes can negatively impact implemented processes. Instead, program to allow the descriptions to
pass through.

BIS123-EN_US — 2 May 2023 Accurint Quick Reference Guide Page 11