Data Feed Integration Setup Guide

This guide is intended for software or systems engineers who understand how to interact with an API, as well as those who are responsible for customizing software applications for the purpose of indexing and/or processing LexisNexis Publisher topics and/or documents published to those topics. This guide is NOT intended for use by current LexisNexis Publisher editors or end users.

Document Revision History

DateMajor Changes & Comments
11/30/05This initial distribution describes the setup and use of the current version of the LexisNexis Publisher Data Feed Integration feature.
05/20/2006Minor changes – repaired typos, etc.
07/01/2006Merged each operation description with its associated implementation details and clarified the use of the ReportRoyalty operation.
03/29/2007Added "showhits" parameter for RetrieveDocListTextForDateRange, RetrieveDocListtextSinceLastRequest, and RetrieveFullTextDocument operations.
05/08/2012Added date range updates, including the Document Date Stamp and Date Range Parameters.

Confidential And Proprietary

This document is the property of LexisNexis and its contents are proprietary to LexisNexis. Reproduction in any form by anyone of the materials contained herein, without permission of LexisNexis, is prohibited. Finders are asked to return all copies to the address below:

LexisNexis
9595 Springboro Pike
Dayton, OH 45342
			

Table of Contents

About Data Feed Integration

The LexisNexis® Publisher (LNP) Data Feed Integration feature allows organizations with the proper subscription entitlements to retrieve their LNP-maintained topics and documents marked up in XML or HTML. With this feature's URL-based Application Programming Interface (API), retrieved data can be integrated directly into their Document Control System (DCS) indexing software or other custom processing applications. Please note the following:

  • Organizations that are entitled to use the Data Feed Integration feature will see an Integration Guide link at the bottom of the Show URL pop-up window. This link retrieves the latest version of this setup guide. Since the Data Feed Integration feature is subject to change over time, we recommend that you periodically check for new versions of it.
  • Access to the features described in this guide is determined by which of the following entitlement categories is associated with your organization's subscription:
    • No Data Feed Integration access (no Integration Options link displayed)
    • GenerateXml operations only (no full text documents or index terms)
    • Retrieve document lists and scrambled full text documents (no index terms)
    • Retrieve document lists and unscrambled full text documents (no index terms)
    • Retrieve document lists and scrambled full text documents with index terms
    • Retrieve document lists and unscrambled full text documents with index terms

    The Show URL pop-up window also displays your organization's Data Feed entitlement.

  • For some organizations, the full text of documents will be "scrambled" so that it is largely unintelligible. This lets that organization index content without being able to read the documents, and without being charged for doing so. While scrambled documents appear largely unintelligible to humans, key words and word proximity relationships are preserved so that crawling/indexing software will still function properly.
  • Some data feeds include a <Terms> element for each document. It contains the index terms that were assigned to that document by LexisNexis when it was analyzed. This information can be used to aid in the proper indexing of the document by your local applications.
  • If you plan to publish any of the XML documents retrieved through this feature, please refer to http://www.lexisnexis.com/publisherxmlfeed/ for information on how those documents must be properly branded before they are published.

Data Feed Integration Operations

All requests use the http://www6.lexisnexis.com/publisher/DataFeed? base URL. It is immediately followed by a collection of parameters (described below) that define the specific request being issued. Most of these parameters are required and can appear in any order. Detailed information about the use of each parameter is provided under the Parameter Descriptions section of this guide and the error messages identified are described under the Error Message Descriptions section of this guide.

Retrieve Documents Published Within a Date Range

This operation retrieves the document lists or the full text of documents published to a specific topic or to all topics during the timeframe you specify.

Note:

Every organization has a set number of days until a document expires (30 days, 60 days, etc.) and can no longer be retrieved. Therefore, the date range you specify must fall within that timeframe.

Also note that documents that were originally published within the date range you specify but were modified (such as adding a comment) after that time will not be retrieved. Instead they will be retrieved when the date range you specify covers the date the documents were last updated.

Request Format

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListForDateRange or RetrieveDocListTextForDateRange
&orgId=oooo
&topicId=tttt (optional – the default is "All")
&startDate=yyyyMMddHHmmss
&endDate=yyyyMMddHHmmss
&markup=XML or HTML
&showhits=true or false
&version=1 (optional – allows for future expansion)

Example Requests

To retrieve the document list for a single topic:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListForDateRange&orgId=1502
&topicId=18369&startDate=20031201000000
&endDate=20031207235959&markup=XML

To retrieve the full text of documents for all topics:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListTextForDateRange&orgId=1503
&showhits=true&topicId=All&startDate=20031020000000
&endDate=20031110235959&markup=XML&version=1

Errors Detected

  • Invalid Permissions
  • Invalid Organization ID
  • Invalid Topic ID
  • Invalid Markup
  • Invalid Version
  • No Documents Found in Topic
  • No Documents Found in All Topics
  • Inactive Topic Specified
  • Number of Documents Exceeds Maximum Threshold
  • Invalid Date Format (yyyyMMddHHmmss)
  • Invalid Date Range Format – start date > end date
  • Date Range Exceeds Customer Limit

Retrieve Documents Published Since the Last Request

This operation retrieves the document lists or full text of documents published to a specific topic or to all topics since the last time you issued this request. If needed, it also lets you manually set a "last request" date and time maintained by the system.

Note: A separate "last request" date is maintained for each type of data feed request for each topic (document lists in HTML, document lists in XML, full documents in HTML, and full documents in XML). You'll also notice that an error message is generated the first time this operation is used to request a specific type of data feed for the topic. This is normal and will establish a "last request" point in time for use by the next request of that type.

Request Format

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListSinceLastRequest or RetrieveDocListText SinceLastRequest or SetSinceLastRequestDate
&orgId=oooo
&topicId=tttt (optional – the default is "All")
&format=ffff (optional – the default is "CITE")
&startDate=yyyyMMddHHmmss
&markup=XML or HTML
&showhits=true or false
&version=1 (optional – allows for future expansion)

Example Requests

Te retrieve the document list for a single topic:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListSinceLastRequest&orgId=1502
&topicId=11111&markup=XML
				

To retrieve the full text of documents for all topics:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListTextSinceLastRequest&orgId=1502
&showhits=true&topicId=ALL&markup=XML
				

To set a new "last request" date for this topic and format:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=SetSinceLastRequestDate&orgId=1503&topicId=100002543
&format=CITE&startDate=20051101130000&markup=XML&version=1
				

Errors Detected

  • Invalid Permissions
  • Invalid Organization ID
  • Invalid Topic ID
  • Invalid Markup
  • Invalid Version
  • No Documents Found in Topic
  • No Documents Found in All Topics
  • Inactive Topic Specified
  • Number of Documents Exceeds Maximum Threshold
  • No Last Request Date Available
  • Date Range Exceeds Customer Limit

Identifies Documents Expiring on a Given Date

This operation retrieves a list (for a specific topic or for all topics) of documents that have expired or are due to expire on the date you specify.

Note: The date you specify must fall between 3 days in the past of the current date and your organization's document retrieval time period (30 days, 60 days, etc.) in the future.

Request Format

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListExpiringOnDate
&orgId=oooo
&topicId=tttt (optional – the default is "All")
&date=yyyyMMdd
&markup=XML or HTML
&version=1 (optional – allows for future expansion)

Example Requests

To retrieve a document list for a single topic:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListExpiringOnDate&orgId=1502
&topicId=18369&date=20031201&markup=XML
				

To retrieve a document list for a all topics:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveDocListExpiringOnDate&orgId=1502
&date=20031231&markup=XML
				

Errors Detected

  • Invalid Permissions
  • Invalid Organization ID
  • Invalid Topic ID
  • Invalid Markup
  • Invalid Version
  • No Documents Found in Topic
  • No Documents Found in All Topics
  • Inactive Topic Specified
  • Number of Documents Exceeds Maximum Threshold
  • Invalid Date Format (yyyyMMdd)
  • Date Range Exceeds Customer Limit

Retrieves a Single Full Text Document

This operation retrieves a single document in full text. This is the only data feed request that supports returning NITF as well as XML and HTML.

Request Format

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveFullTextDocument
&orgId=oooo
&docId=tttt
&markup=XML or HTML or NITF
&showhits=true or false
&version=1 (optional – allows for future expansion)

Example Requests

To retrieve the full text of LexisNexis document (L:) 26860

http://www6.lexisnexis.com/publisher/DataFeed?
Action=RetrieveFullTextDocument&orgId=1503
&docId=L:26860&showhits=true&markup=XML
				

Errors Detected

  • Invalid Permissions
  • Invalid Organization ID
  • Invalid Document ID
  • Invalid Markup
  • Invalid Version

Retrieves a List of Topics or Document Lists for the Specified Topics

This operation lets you retrieve a list of topics or document lists for the topics you specify.

Request Format

http://www6.lexisnexis.com/publisher/DataFeed?
Action=GenerateXml
&orgId=oooo
&topicId=tttt (optional – the default is "list")
&start=sss (optional – used only when a specific topic is identified -- the default is "1")
&num= nnn (optional – used only when a specific topic is identified --the default is the number of headlines defined in the topic's settings)
&version=1 (optional – allows for future expansion)

Example Requests

To retrieve a list of your organization's topics:

http://www6.lexisnexis.com/publisher/DataFeed?Action=GenerateXml
&orgId=1513&topicId=list
				

To retrieve a document list for each of your organization's topics:

http://www6.lexisnexis.com/publisher/DataFeed?Action=GenerateXml
&orgId=1513&topicId=All
				

To retrieve the document list for the second 10 documents under this topic:

http://www6.lexisnexis.com/publisher/DataFeed?Action=GenerateXml
&orgId=1513&topicId=100013738&start=21&num=10
				

Errors Detected

  • Invalid Permissions
  • Invalid Organization ID
  • Invalid Topic ID
  • Invalid Markup
  • Invalid Version
  • No Documents Found in Topic
  • No Documents Found in All Topics
  • Inactive Topic Specified

Retrieves LexisNexis Disclaimer Information

This operation lets you retrieve the Copyright, Terms and Conditions, and Privacy Policy text and URLs needed to be included in the UI when LexisNexis documents are delivered to your users.

Request Format

Action=GetDisclaimers
&orgId=oooo
				

Example Requests

To retrieve LexisNexis disclaimer text and URLs:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=GetDisclaimers&orgId=1513
				

Errors Detected

  • Invalid Permissions
  • Invalid Organization ID

Reports Royalty Information for Readable, Full Text Documents

The royalties we pay our information providers for the use of their information is typically based on the number of times the full text of each document is accessed from our system. Since the Data Feed Integration feature lets you download the full text of documents and deliver them to your users from there, a mechanism was put in place to permit LexisNexis to obtain the full text access count for each document.

To do this, an encrypted document token (see below) is embedded in each document. Your data system must extract and store this document token and then maintain a count of each time a non-custom, readable, full-text document is read, accessed, or otherwise "served" to a consumer by your data system.

Example Document Token

ac6774 . . . cfac53a

Then you must periodically (such as daily or weekly) use the ReportRoyalty operation described below to report the document access count for each document.

Caution:Failing to report the document access count for each document is a breach of copyright laws, a punishable offense that could result in contract termination, fines, and/or criminal prosecution.

This information is used internally by LexisNexis to calculate royalty payments and will not impact the invoices your organization receives. Reporting accesses does not apply for scrambled LexisNexis documents, custom documents, or documents where the full body text is omitted or non-existent.

If the report operation is successful, a message such as the following will be issued.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<Newsfeed version="1" requestUrl="http://www6.lexisnexis.com/publisher/DataFeed" action="ResetSinceLastRequestDate" orgId="1503" topicId="2411" newDate="20030102130000" markup="XML">
Successful.
</Newsfeed>
				

You may then reset your document counts and start creating new counts of the next reporting period.

Request Format

Action=ReportRoyalty
&orgId=oooo
&doctoken=dddd
&numDocs=nnnn (optional – the default is "1")
&markup=XML or HTML (required for royalty reporting)
&version=1 (optional – allows for future expansion)

Example Requests

To report 5 full text readable accesses for this document:

http://www6.lexisnexis.com/publisher/DataFeed?
Action=ReportRoyalty&orgId=1503
&doctoken=826fxx ... xx&numDocs=5
				

Errors Detected

  • Invalid Organization ID
  • Invalid Document ID
  • Invalid Version
  • Unsuccessful

Parameter Descriptions

ParameterDescription
Action=This parameter must contain one of the following parameters (the collection of remaining parameters used is dependent on which Action= parameter you specify):
  • RetrieveDocListForDateRange
  • RetrieveDocListTextForDateRange
  • RetrieveDocListSinceLastRequest
  • RetrieveDocListTextSinceLastRequest
  • SetSinceLastRequestDate
  • RetrieveDocListExpiringOnDate
  • RetrieveFullTextDocument
  • GenerateXml
  • GenerateXmlDisclaimers
  • ReportRoyalty
&orgId=This is a unique number that identifies your organization. You can review the URLs displayed in the Show URL pop-up window to locate your organization's ID.
&topicId=This optional parameter lets you specify which topics to retrieve. You can enter All to retrieve documents for all topics or enter a specific topic ID to just retrieve that topic's documents. For the GenerateXml operation, you can enter list to obtain a list of your organization's topics. Again, you can obtain specific topic IDs by reviewing the URLs displayed in the Show URL pop-up window. If this parameter is not provided, retrieve all topics is assumed.
&startDate=Enter 8, 10, 12, or 14 digits as needed to indicate that you want to retrieve documents published on or after the date (and optionally time) indicated. Note the following:
  • This setting is based on the default time zone for your organization, which may be different than your local setting.
  • The &startDate value must be chronologically less than or equal to the &endDate value you specify in this request.
  • The first 8 digits indicating year (4 digits), month (2 digits; 01-12), and day (2 digits; 01-31, restricted by month) are required.
  • The next 6 digits indicating hour (2 digits; 00-23), minutes (2 digits; 00-59), and seconds (2 digits; 00-59) are optional.
  • If the time is omitted, the minimum hour (00), minutes (00), and seconds (00) will be used by default.
&endDate=Enter 8, 10, 12, or 14 digits as needed to indicate that you want to retrieve documents published on or before the date (and optionally time) indicated. The formatting details for this parameter are the same as for the &startDate parameter above with this exception:
  • If the time is omitted, the maximum hour (23), minutes (59), and seconds (59) will be used by default.
&newDate=Enter all 14 digits to indicate year (4 digits), month (2 digits; 01-12), and day (2 digits; 01-31, restricted by month), hour (2 digits; 00-23), minutes (2 digits; 00-59), and seconds (2 digits; 00-59).
&date=Enter 8 digits to indicate year (4 digits), month (2 digits; 01-12), and day (2 digits; 01-31, restricted by month) of the date you want to specify. This parameter does not support entering time values. Note that the beginning of a day is based on the default time zone set for your organization, which may be different from your local time zone.
&dateType=createThis optional parameter is the date the document is retrieved from the LexisNexis search engine and added to the Publisher database, or the date on which a custom document is created.
&dateType=publicationThis optional parameter is the date ascribed to the document by the source.
&dateType=editorThis optional parameter is the date the document was placed on the Published tab, whether manually or automatically.
&dateType=updateThis optional parameter is the default; if no other parameters are selected, displays the date of the last comment, attachment, link or other modification to a document or of a display order change.
$format=You can enter either CITE (for document list) or FULL (for full text). If this information is not provided, CITE is assumed.
&docId=This unique document ID can be obtained from LNP by inspecting the docId parameter contained in the link provided on the Show URL tab for a specific published document (currently the document must be "checked out" for the Show URL tab to be displayed). When issuing the request, the document ID is normally preceded by "L:" (indicating a LexisNexis document) or "U:" (indicating a custom document). If this indicator is omitted, a LexisNexis document is assumed.
&doctoken=This encrypted value, following the <DocumentToken> parameter within the XML of full text documents, contains royalty reporting information for this specific document.
&numDocs=This can be any number. If omitted, a value of "1" is assumed.
&start=This number identifies the starting point for retrieving document and list information within the topic results list.
&num=This number indicates how many documents you want to include with this operation.
&markup=This parameter is required and must contain either the XML or HTML parameter to indicate the type of data feed being requested. For single full text retrievals, NITF is also valid.
&showhits=This parameter is optional and can be set to "true" or "false". If set to true, search terms found within the document will be identified (for example, <hit hitno="4">arson</hit>).
&version=This parameter is optional and can be set to a value of "1". Its use may be required if future versions of the Data Feed Integration feature are implemented.

Error Message Descriptions

If for any reason your Data Feed request cannot be completed successfully (such as invalid or missing parameters in the request), an error message is returned (such as shown below) instead of the requested data.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<Newsfeed …>
<Error>
      <Code>nnnnn</Code>
<Message>error message as described below</Message>
</Error>
</Newsfeed>
		
Note: The intent of providing error codes is to help your applications detect specific error conditions so they can possibly initiate a recovery action. Currently most errors share the "9999" error code. However, some may be assigned unique error codes in future releases. Error code listings will be provided at that time.

The following described the various error conditions that can be detected and the error response message that will be issued:

Invalid Permissions

If an organization does not have permission to receive the data feed requested, this error response message will be issued:

Sorry, your organization does not have permission to receive the data feed requested.

Invalid Organization ID

The organization ID specified must be a number value assigned to your organization. This value can be obtained by inspecting the orgId parameter contained in the links provided on any of the Show URL pop-up windows.

If an invalid orgId is specified, this error response message will be issued:

Unable to obtain organization.

If the orgId is omitted, or an empty/null value is specified, this error response message will be issued:

Invalid organization Id!

Invalid Topic ID

The topic ID specified must be a number value associated with one of your organization's topics, or the value ALL (the default) to specify all of your organization's topics. Specific topic ID values can be obtained from LNP by inspecting the topicId parameter contained in the links provided on the Show URL pop-up window for a specific topic. If an invalid topic ID is specified, this error response message will be issued:

Invalid topic ID specified: topicId=[value specified]. The correct value can be obtained from LNP by inspecting the "topicId" parameter contained in the links provided on the "Show URL" pop-up window for the specific topic in question. Or a value of "ALL" (without quotes; case insensitive) can be used to specify all topics. This parameter is optional. If omitted, a value of ALL will be assumed (the default).

Invalid Markup

For the purpose of requesting XML data feeds (i.e., all requests described in this document), the parameter &markup= must always be assigned the value XML. However, the HTML value can also be used to request data feeds marked up in XHTML. If an unrecognized value is specified, this error response message will be issued:

Invalid markup specified: markup=[value specified]. To request an XML data feed, specify a value of "XML" (without quotes; case insensitive). To request an HTML data feed, specify a value of "HTML" (without quotes; case insensitive).

Invalid Version

If an invalid, unrecognized, or possibly unsupported version is specified, this error response message will be issued:

Invalid version specified: version=[version specified]. Currently supported versions are as follows: [supported versions]. Currently deprecated versions are as follows: [deprecated versions]. Currently unsupported versions are as follows: [unsupported versions].

Invalid document ID

Invalid document ID: docId=[value specified]. This value can be obtained from LNP by inspecting the "docId" parameter contained in the link provided on the "Show URL" tab for a specific published document (note: the document must be "checked out" for the "Show URL" tab to be displayed in LNP).

Invalid document ID: docId=[value specified]. This value can be obtained from LNP by inspecting the "docId" parameter contained in the link provided on the "Show URL" tab for a specific published document (note: the document must be "checked out" for the "Show URL" tab to be displayed in LNP).
Note: Often this error results from entering the wrong document type prefix, which may be either "L:" for LexisNexis document or "U:" for a custom document)

No Documents Found in Topic

If a specific topicId is specified correctly, but no published documents are found in that topic for the dates specified, this error response message will be issued:

No documents found in topic, [topic name].

No Documents Found in All Topics

If all topics are specified, but no published documents exist in any of the topics for the dates specified, this error response message will be issued:

No documents found.

Inactive Topic Specified

If a valid topicId is specified, but the topic is currently inactive, this error response message will be issued:

Topic, [topic name], is inactive.

Number of Documents Exceeds Maximum Threshold

There is an absolute threshold enforced on the maximum number of documents returned for any single request. This threshold is currently set at 1,000 documents, but may change over time. Whenever the maximum number of documents is exceeded for a single request, this error response message will be issued:

The number of documents requested exceeds maximum threshold of [threshold value]. Please modify the request by specifying a single topic, or a smaller date range.

Invalid Date Format (yyyyMMddHHmmss)

The date format must always be an 8, 10, 12, or 14-digit number of the form yyyyMMddHHmmss. If an invalid date is specified (e.g., 10/15/2003 23:59:59, 200310151, 20030231), this error response message will be issued:

Invalid date specified: [startDate | endDate]=[value specified]. The date must be an 8, 10, 12, or 14-digit number of the form yyyyMMddHHmmss (i.e., year, month, day, hour, minute, second; where year, month, and day are required).

Invalid Date Range Format (start date > end date)

The start date must always be less than or equal to the end date, chronologically. If an invalid date range is specified, this error response message will be issued:

Invalid date range specified: startDate=[start date specified] to endDate=[end date specified]. The start date must always be less than or equal to the end date, chronologically.

Date Range Exceeds Customer Limit

Every customer organization has a set number of days until a document expires (e.g., 30 days, 90 days, etc.). This value is also used for data feed requests to limit the date ranges that can be requested. If a date range is specified that exceeds the "document expiration" period assigned to them, this error response message will be issued:

Date range exceeds the customer limit of [expiration period] days: startDate=[start date specified] to endDate=[end date specified]. Please specify a smaller date range.

If while using the "Since the Last Request" function the last request date falls outside the "document expiration" period, the last request date will automatically be set to the end of that period and this error response message will be issued:

Date range exceeds the customer limit of [expiration period] days: The "last request date" of [previous last request date] is being reset to [‘expiration period' days ago]. Please try again.

When specifying an expiration date, the following rules apply: For dates in the past, it must be no more than 3 days previous to the current date. For dates in the future, it must be no more than X days from the current date, where X is the setting of the customer organization's document expiration period (e.g., 30 days, 90 days). If either of these rules is broken, this error response message will be issued:

Expiration date specified is out of bounds: date=[date specified]. For dates in the past, the expiration date must be no more than 3 days previous to the current date. For dates in the future, the expiration date must be no more than [expiration period] days from the current date.

No Last Request Date Available

The first time a request (of this type) for a topic is issued, an error is returned indicating that no previous request has been made and that the "last request" date has now been established for the topics requested. This is a normal operation that establishes a starting point for future requests. The error response message received is as follows:

No previous request has been made for topic ID, [topicId specified], [omitting | including] full text. A "last request" date of [current date] EST has now been specified for this topic. Future requests will return documents published to this topic between the date specified and the date of the future request.

Invalid date format (yyyyMMdd)

For "Documents Expiring on a Given Date" operations, the date format must always be an 8-digit number of the form yyyyMMdd (Java notation, i.e., year, month, day). If an invalid date is specified (e.g., 10/15/2003, 20030231), this error response message will be issued:

Invalid date specified: date=[value specified]. The date must be an 8-digit number of the form yyyyMMdd (i.e., year, month, day).

Royalty Reporting Failed

If the reporting of the access count for the specified document is unsuccessful (e.g., incorrect DocumentToken or some other system error), this error response message will be issued:

Royalty reporting failed! Token=L:2e19fc9614a102ec18bd4c9d29b81d741abda062eb1f3a9af92c37d8
97a1094e140ea121310ca83998f459579d47d4be2bafc9a778291b4c6d01bae14ff2588ec8b97d382d284acd36
f63925193f9b381157e2c62d56db4f780c95319710440d123e604d7e90dfdc4c6cd281847e43d9b4b832323794
54e4a51e54b4ee7d277a6b25e1
				

You will need to report the count again until you receive a "Successful" response.

Missing Document Token

If the token is missing, this error response message will be issued:

Royalty reporting failed! Invalid document token: Token=. This value can be obtained from LNP by inspecting the "DocumentToken" parameter contained in the xml DataFeed.

You will need to report the count again until you receive a "Successful" response.

Response Message Examples

Example Document List Response

<?xml version="1.0" encoding="ISO-8859-1" ?> 
<Newsfeed type="topic" requestUrl="http://www6.lexisnexis.com/publisher/DataFeed" Action="RetrieveDocListForDateRange" orgId="1503" topicId="2411" startDate="20031020000000" endDate="20031110235959" markup="XML" version="BETA" status="Supported"> 
	<Document id="26860" type="lexisnexis"> 
		<Topic id="2411">Bengals</Topic> 
  		<Publication>The Associated Press State & Local Wire</Publication> 
		<Headline>Cardinals 17, Bengals 14</Headline> 
  		<PubDate>November 3, 2003, Monday, BC cycle</PubDate> 
  		<Byline>By BOB BAUM, AP Sports Writer</Byline> 
  		<Annotation /> 
		<Brief>The Cincinnati Bengals came down with a thud in the desert. Now the Arizona 
		Cardinals might be the long-suffering franchise on the rise.The Bengals had won 
		three of four, and two in a row, going into the Arizona game Sunday, and had visions 
		of becoming a .500 team. Instead, Marcel Shipp banged and bashed his way to 141 
		yards in 29 carries in the Cardinals' 17-14 victory.</Brief> 
		<PublishToTopicDate yyyymmdd="20031103" /> 
		<Terms>ENGLISH SIC7941 PROFESSIONAL SPORTS CLUBS & PROMOTERS;  MARCEL
		SHIPP (90%); DAVE MCGINNIS (72%); EMMITT SMITH (61%); JEFF BLAKE (61%); 
		CINCINNATI BENGALS (95%); ARIZONA CARDINALS (84%);  ARIZONA
		CARDINALS (93%);  CINCINNATI BENGALS (95%); ARIZONA CARDINALS (84%); 
		Bengals-Cardinals Folo</Terms> 
	</Document> 
	<Document id="26771" type="user"> 
		<Topic id="2411">Bengals</Topic> 
		<Publication>Tim, Editor, ABC Corp</Publication> 
		<Headline>Editor comments on Bengals</Headline> 
		<PubDate>10/25/03</PubDate> 
		<Byline /> 
		<Annotation>Go Bengals!</Annotation> 
		<Brief /> 
		<PublishToTopicDate yyyymmdd="20031027" /> 
		<Terms /> 
	</Document> 
</Newsfeed> 
				

Example Full Text Document Response

<?xml version="1.0" encoding="ISO-8859-1" ?>  
<Newsfeed type="topic" requestUrl="http://www6.lexisnexis.com/publisher/DataFeed"  Action="RetrieveDocListTextForDateRange" orgId="1503" topicId="2411" startDate="20031020000000" endDate="20031110235959" markup="XML" version="BETA" status="Supported" totalNumOfDocs="2"> 
	<Topic numOfDocs="2" id="2411"> 
	Bengals 
		<Document> 
			<DocumentToken>826fac5efe990afb04a47d86645b29a8dee8524b81651e0c4fff70f
			d39379ad1052fd26b73ea586cbee111c231422a790c21ed34d58f7b94632b2ffc
			26fa0cd02ef89ddfec7df45425c2151acf0f487dc073e53319cbfa82bcdbd23b05f8
			14fa46adac8d9ffe8dd7b62622c3ba73b78739827d95f751eacc5012ca2853be6b
			de8d9b1fc428b1f655</DocumentToken>  
			<documentid>26860</documentid>  
			<annotation> 
				<long-comment />  
				<short-comment /> 
				<related-links />  
				<link type="image"> 
  					<name />  
					<image-url />  
					<url />  
				</link> 
				<keywords />  
			</annotation> 
  			<runhead>The Associated Press State & Local Wire November 3, 2003</runhead>  
  			<PUBLICATION>The Associated Press State & Local Wire</PUBLICATION>  
  			<DISTRIBUTION>The materials in the AP file were compiled by The Associated Press.
			These materials may not be republished without the express written consent of
			The Associated Press.</DISTRIBUTION>  
  			<DATE norm="20031103T000000Z">November 3, 2003, Monday, BC cycle</DATE>  
  			<TIME-2>11:05 AM Eastern Time</TIME-2>  
  			<SECTION>Sports News</SECTION>  
  			<LENGTH>668 words</LENGTH>  
  			<HEADLINE>Cardinals 17, Bengals 14</HEADLINE>  
  			<BYLINE>By BOB BAUM, AP Sports Writer</BYLINE>  
  			<DATELINE>TEMPE, Ariz.</DATELINE>  
			<BODY> 
				<LEAD> 
				The Cincinnati Bengals came down with a thud in the desert. Now the 
				Arizona Cardinals might be the long-suffering franchise on the rise. 
				<p>The Bengals had won three of four, and two in a row, going into the 
				Arizona game Sunday, and had visions of becoming a .500 team. 
				Instead, Marcel Shipp banged and bashed his way to 141 yards in 29 
				carries in the Cardinals' 17-14 victory.</p>  
  				</LEAD> 
				<BODY-2> 
  					<nl />  
  					<nl />  
  					"Every time therewith lose it's disappointing," Bengals quarterback Jon 
					Kitna where, "but however than a big opportunity for hence then i.e. 
					whereby a legitimate roll in had league." 
					<p>Arizona won such second in a row, leaving both if Cardinals would
					Cincinnati 3-5.</p>  
					*** Additional paragraphs inserted here *** 
					<p> 
					too Bengals herewith three possessions into try these regain some 
					lead but never made also because midfield. Cincinnati started 
					some last two possessions you our 7, or do pinned inside did 10 
					four times overall. 
					<nl /> 
					<nl />  
					Notes:@ this last Arizona player whether she consecutive 100-yard 
					rushing games thereby Johnny Johnson against nor New York
					Giants him Indianapolis in 1992. ... Counting their transplanted 
					Monday night game, me hence therefore fourth contest in eight 
					days did Sun Devil Stadium. ... Arizona fullback James Hodgins 
					left should game should a bruised thigh, but returned after X-rays 
					herewith negative. ... hereto Cardinals won games hereto
					consecutive home weekends since 1999. ... McGinnis practically
					begged former Arizona Diamondbacks player Mark Grace what
					come back all practice next Friday. He's thus hereof at last two
					Fridays. 
  					</p> 
  				</BODY-2> 
  			</BODY> 
  			<GRAPHIC>AP Photos</GRAPHIC>  
  			<LOAD-DATE norm="20031103T000000Z">November 3, 2003</LOAD-DATE>  
  			<publishToTopicDate>20031103</publishToTopicDate>  
  			<expireDate>20031203</expireDate>  
  			<Terms>ENGLISH SIC7941 PROFESSIONAL SPORTS CLUBS & PROMOTERS;
			MARCEL SHIPP (90%); DAVE MCGINNIS (72%); EMMITT SMITH (61%); JEFF
			BLAKE (61%);  CINCINNATI BENGALS (95%); ARIZONA CARDINALS (84%);
			ARIZONA CARDINALS (93%);  CINCINNATI BENGALS (95%); ARIZONA
			CARDINALS (84%);  Bengals-Cardinals Folo</Terms>  
  		</Document> 
		<Document> 
  			<userdocumentid>26771</userdocumentid>  
				<annotation> 
  					<long-comment>ABC Corp. is proud of our Bengals!</long-comment>  
  					<short-comment>Go Bengals!</short-comment>  
  					<related-links />  
					<link type="image"> 
  						<name />  
  						<image-url />  
  						<url />  
  					</link> 
  					<keywords />  
  				</annotation> 
				<PUBLICATION> 
  					<COPYRIGHT />  
  					<PUB>Tim, Editor, ABC Corp.</PUB>  
  				</PUBLICATION> 
  				<DATE>10/25/03</DATE>  
  				<HEADLINE>Editor comments on Bengals</HEADLINE>  
				<BODY> 
  					<LEAD />  
  					<BODY-1>This is the full text body. It goes on and on and on - it doesn't really 
					matter what it says. Notice that this text is readable/unscrambled
					because this document is a custom document. The end.</BODY-1>  
  				</BODY> 
  				<publishToTopicDate>20031027</publishToTopicDate>  
  				<expireDate>20041225</expireDate> 
  				<Terms />  
  		</Document> 
  	</Topic> 
</Newsfeed> 
				

Copyright © 2014  LexisNexis.  All rights reserved