What is Semantria API?
Semantria API is a RESTful Web API, providing SaaS text analysis, text mining, and sentiment analysis capabilities to its customers. Semantria uses a modified/scalable version of Lexalytics Salience Engine (top NLP/text analytics engine, used by Microsoft, Thomson Reuters, Cisco, Salesforce.com/Radian6) to enable the extraction of Entities, Concept Topics, Query Topics, Concept Matrix, Themes, Summaries, and Sentiment, all while supporting Multiple Languages and other NLP functionality. As an SaaS text analysis tool, Semantria is located on Amazon EC2, and includes real-time scalability, load balancing, billing, client/account management, .Net, Java, Python, PHP, and Ruby API wrappers among its infrastructure.
Interested to learn more about Semantria's SaaS text & sentiment analysis API? Visit API Principles and API Status.
Is there a demo? How do I try it out?
We offer a fully functional Trial Version (10,000 API transactions).
What languages does Semantria API support?
Semantria API currently supports English, French, Spanish, Portuguese, Italian, German, Mandarin, Korean, and Japanese. We also have partners that offer Malay, Indonesian, and Singlish.
Can I use Semantria API for commercial purposes?
Yes, Semantria API may be utilized for both personal and commercial purposes, as long as you abide by our API Service Agreement.
How does the API retrieve data?
There are 3 different methods to retrieve data which are described in API Integration and the processing time is indicated in Real-Time Solution.
What are the usage limits? How many API transactions am I allowed to make each day?
There are no usage limits with Semantria API. You pay for a certain amount of transactions (cost per transactions decreases with volume) and then can use them as needed.
Is any special access available for nonprofits?
We offer special rates for educational institutions. Inquire for more information.
How much text does Semantria API require to generate results?
Semantria API can process text that is as small as a 140 character tweet or SMS message and as large as a 65,535 character text in UTF 8 encoding. The processing lag is directly proportionate to the amount of text.