Documentation Release Notes Downloads FAQs

Acceptable Use Policy

Last revised: May 31, 2018

You may process transactions using the Service for your own internal use or on behalf of your customers.

You warrant that, for each transaction subject to the European GDPR, the data owner has consented to such processing (which may have been obtained by your customer or another party), and you will not knowingly process any data that belongs to a person of less than adult legal age. You may not send data to the Services for vendor-specific geocoding that does not comply with that vendor's terms of service and acceptable use policies.

You may not use the Service, or the results obtained from use of the Service in whole or in part, in or in conjunction with, or as a part of, any system, method, manner, or process of any kind which violates the intellectual property rights, privacy rights or other legally enforceable rights of any third party, and you agree to indemnify, defend and hold harmless Provider from all claims, allegations, proceedings, judgments, settlements, and damages of any and every kind arising therefrom.

You may not use the Services or the results of the Services in any system, business or process which, in the opinion of Provider, has the intent or effect of reducing or potentially reducing, the demand of other third parties for Provider's parsing software or services.

You agree to safeguard the credentials to the Service to prevent their theft or misuse.

You may not knowingly send malformed documents, nor documents containing malicious code, nor unsupported document types to the Service.

You may not re-submit a document to the Service if (1) a prior processed transaction of that document contained a return code from the Service indicating that the document was corrupt or of an unsupported type, or (2) the document text field in the response was empty, or (3) the transaction returned an exception which included this phrase: "System.Net.WebException: The underlying connection was closed".

You may not in any way attempt to reverse engineer or otherwise re-create the Sovren skills lists during your use of the Sovren Skills Editor, nor by any other method. Any attempts to re-type, copy and paste, create screenshots, etc., are strictly prohibited.

You may not "ping" the Service more than once a day, nor retrieve the WSDL from the Service more than once per day, nor retrieve your account information (REST | SOAP) more than twice per day unless in conjunction with a Batch Transaction.

You may not use the Service to process documents unrelated to recruitment. You may not perform scalability testing of any kind, nor process any transactions through the Service with the intent of determining when the Service will or is likely to become overwhelmed.


"Ad Hoc Transaction" refers to a transaction that is initiated, using the credentials we provided you, due to a single Service end-user submitting a single document that is immediately sent or forwarded to the Service for processing. An Ad Hoc Transaction is a transaction that by its very nature is not scheduled or controlled by Recipient as to time of submission. A candidate uploading her resume would be a typical kickoff for an Ad Hoc transaction.

Ad Hoc Transactions are not subject to the concurrency limitations on Batch Transactions, and may be submitted at any time, even during a Batch Transaction, and in no case will Ad Hoc Transactions be counted against the Maximum Allowable Number of Concurrent Batch Transactions.

A "Batch Transaction" is any transaction that is not an Ad Hoc Transaction, such as a transaction submitted to the Service for processing by a program that is iterating through and submitting multiple documents to the Service for processing. In such case, each such document submitted constitutes a separate Batch Transaction. [For a sample program with full source code to process batch transactions, contact]

You may not submit more than the Maximum Allowable Number of Concurrent Batch Transactions to the Service. In order to determine your current Maximum Allowable Number of Concurrent Batch Transactions, you must programatically retrieve your account information from the Service (RESTSOAP) and obtain the MaximumConcurrentRequests value that is returned, immediately prior to processing Batch Transactions, and after every 1000 transactions processed within the batch.

In other words, once you have submitted the Maximum Allowable Number of Concurrent Batch Transactions to the Service ("the current transactions"), an additional Batch Transaction, whether from the same process or any other batch process submitting with your credentials, may be submitted only when, and as, the Service has returned the results of its processing of one of the submitted transactions.

You may request larger levels of Maximum Allowable Number of Concurrent Batch Transactions to the Service. If you need to run, say, a batch of 1,000,000 transactions by submitting 1000 concurrent transactions, we can work with you to allow this (with sufficient advance notice, and in rare cases for a fee to cover increased hosting costs, if we estimate that such will be required).

You may submit unlimited Ad Hoc transactions to the AI Matching endpoints (search, bimetric scoring, or AI Matching). You may not submit more than 100 non-Ad Hoc search, bimetric scoring, or AI Matching transactions per day unless you prior negotiate a higher limit with us.


Violation of any part of this Acceptable Use Policy, intentionally or unintentionally, shall be grounds for immediate suspension or termination of your access to the Service. We may suspend and/or terminate you if Provider determines that you are using the Service in such a way as to negatively impact our ongoing business interests or competes against the Service. Suspension and/or termination of access are at our sole discretion.