Geneea

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.…

AI & machine learning#openapi#text

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

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 <YOUR_API_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 &longrightarrow;
Finds out lemmata (basic forms) of all the words in the document.

correction &longrightarrow;
Performs correction (diacritization) on all the words in the document.

topic detection &longrightarrow;
Determines a topic of the document, e.g. finance or sports.

sentiment analysis &longrightarrow;
Determines a sentiment of the document, i.e. how positive or negative the document is.

named entity recognition &longrightarrow;
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
Content-Type: application/json

{"text":"There is no harm in being sometimes wrong - especially if one is promptly found out."}

This is equivalent to GET /s1/sentiment?text=There%20is%20no%20harm...

Request limitations

The API has other limitations concerning the size of the HTTP requests. The maximum allowed size of any
POST request body is 512 KiB . For request with a URL resource, the maximum allowed number of
extracted characters from each such resource is 100,000 .

Terms of Service

By using the API, you agree to our
Terms of Service Agreement .

More information

The Interpretor Public Documentation

Endpoints 12

account

  • GETInformation about current user account/accountgetInfo

geneea-api-s1

  • GETPerforms text correction (diacritization) on the given document/s1/correction?id=string&text=string&url=string&extractor=default&language=string&returnTextInfo=true<br/><strong>Possible options:</strong><p class="markdown">An optional parameter <code>diacritize</code> with values <code>yes</code>, <code>no</code> or…
  • POSTPerforms text correction (diacritization) on the given document/s1/correction<strong>Notes:</strong><br/>Valid JSON cannot contain newline characters. These have to be escaped. (See also <a…
  • GETPerforms named-entity recognition on the given document/s1/entities?id=string&text=string&url=string&extractor=default&language=string&returnTextInfo=trueentitiesGet
  • POSTPerforms named-entity recognition on the given document/s1/entities<strong>Notes:</strong><br/>Valid JSON cannot contain newline characters. These have to be escaped. (See also <a…
  • GETPerforms lemmatization on the given document/s1/lemmatize?id=string&text=string&url=string&extractor=default&language=string&returnTextInfo=truelemmatizeGet
  • POSTPerforms lemmatization on the given document/s1/lemmatize<strong>Notes:</strong><br/>Valid JSON cannot contain newline characters. These have to be escaped. (See also <a…
  • GETPerforms sentiment analysis on the given document/s1/sentiment?id=string&text=string&url=string&extractor=default&language=string&returnTextInfo=truesentimentGet
  • POSTPerforms sentiment analysis on the given document/s1/sentiment<strong>Notes:</strong><br/>Valid JSON cannot contain newline characters. These have to be escaped. (See also <a…
  • GETPerforms topic detection on the given document/s1/topic?id=string&text=string&url=string&extractor=default&language=string&returnTextInfo=truetopicGet
  • POSTPerforms topic detection on the given document/s1/topic<strong>Notes:</strong><br/>Valid JSON cannot contain newline characters. These have to be escaped. (See also <a…

status-api

  • GETGets status of the Interpretor service/statusstatus

API details

Base URL
https://api.geneea.com
Authentication
An API key in the user_key query parameter
Operations
12 operations on 7 pathsGET 7POST 5
Main resources
geneea-api-s1 10account 1status-api 1
Description format
Swagger 2.0, API version 1.0
Listed from
APIs.guru OpenAPI Directory (CC0-1.0)
Source updated

How to test the Geneea Natural Language Processing in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Geneea Natural Language Processing collection, without the publisher's secrets.
  3. Add your credentialsThis API uses an API key in the user_key query parameter. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Information about current user account” (GET /account), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the 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.… It is listed under AI & machine learning and has 12 endpoints.

Who publishes the Geneea Natural Language Processing?

It is listed from Geneea's public API description (an OpenAPI document), not published by Geneea on Swastik Codes. Anyone who controls geneea.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Geneea Natural Language Processing?

Requests go to https://api.geneea.com. Endpoint paths are added to this base URL.

How do I authenticate with the Geneea Natural Language Processing?

With an API key in the user_key query parameter.

How many endpoints does the Geneea Natural Language Processing have?

12 operations on 7 paths (7 GET, 5 POST). The largest groups are geneea-api-s1, account, status-api.

Is forking the Geneea Natural Language Processing free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.