API Frequently Asked Questions (FAQ)

Q: Does the API make licensing claims to any submitted content?
A: No. Unlike other content driven APIs, the TextWise API makes no licensing claims or distribution claims to content that is submitted to the API.

Q: How are calls to the API counted against the token?
A: The maximum number of API calls that can be made for a token is 20,000 per 24 hour period, at a rate not to exceed 5 queries per second. The 24 hour period resets at 12:00 am Eastern Standard Time. If your application requires more than 20,000 calls to be made within a 24 hour period, please contact us for available licensing options for additional queries.

Q: Does the API store or index submitted content?
A: The TextWise API does permanently store, within a database, content that is submitted to the API for custom indexing using the Semantic Gist® matching engine. This content is stored in order to allow the system to automatically retrain the semantic model that is used by the Semantic Gist® matching engine. Retraining occurs when new content is added to the index that would cause the semantics of the index to drift and thus reduce the relevance of the matches.

Please review our privacy policy for more information.

Q: Do I need a new token to take advantage of new functionality?
A: Your existing token can be used to access the new functionality in our general releases.  There is no need to re-register or request a new token.

Q: Where can I find my API token?
A: The API token is created for an account once you register with the TextWise API and is displayed on your account page detail once you login to SemanticHacker.com.

Q. Why don't live loads that generate an error code 414, "Too Many Items For Live Update," show up under the Upload Index tab of the Reporting page?

A. This is by design. The error code is only returned in response to the request. The Upload Index tab shows only valid API load requests.

Q: What languages does the API support?
A: The API currently only supports English.