Geneea Natural Language Processing
Authentication For all calls, supply your API key. Sign up to obtain the key . Our API supports both unencrypted (HTTP) and encrypted (HTTPS) protocols. However, for security reasons, we strongly encourage using only the encrypted version. The API key should be supplied as either a request parameter user_key or in Authorization header. Authorization: user_key API operations All API operations can perform analysis on supplied raw text or on text extracted from a given URL. Optionally, one can supply additional information which can make the result more precise. An example of such information would be the language of text or a particular text extractor for URL resources. The supported types of analyses are: lemmatization ⟶ Finds out lemmata (basic forms) of all the words in the document. correction ⟶ Performs correction (diacritization) on all the words in the document. topic detection ⟶ Determines a topic of the document, e.g. finance or sports. sentiment analysis ⟶ Determines a sentiment of the document, i.e. how positive or negative the document is. named entity recognition ⟶ Finds named entities (like person, location, date etc.) mentioned the the document. Encoding The supplied text is expected to be in UTF-8 encoding, this is especially important for non-english texts. Returned values The API calls always return objects in serialized JSON format in UTF-8 encoding. If any error occurs, the HTTP response code will be in the range 4xx (client-side error) or 5xx (server-side error). In this situation, the body of the response will contain information about the error in JSON format, with exception and message values. URL limitations All the requests are semantically GET . However, for longer texts, you may run into issues with URL length limit. Therefore, it's possible to always issue a POST request with all the parameters encoded as a JSON in the request body. Example: POST /s1/sentiment Cont
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- apisguru:geneea.com
- Listed in
- APIs.guru
- Publisher
- geneea.com
- Latest version
- 1.0
- Published
- 2019-02-13
- Evidence
- Listed only, not analyzed yet
What a full analysis of Geneea Natural Language Processing checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.