Skip to main content

General API: Reference

The General API (G3) is a general-purpose Natural Language Understanding (NLU) API. It provides a wide range of linguistic analyses, from basic language detection to complex relation extraction and semantic tagging.

Authorization​

All requests to the General API must include a valid API key. You can provide the key either as a user_key request parameter or via the Authorization header:

Authorization: user_key <YOUR_API_KEY>

Functions​

The table below summarizes the available endpoints in the General API. These endpoints allow you to perform various analyses on individual documents or batches of text.

EndpointDescription
Request200 Response
Account: Information about your subscription
GET /accountReturns information about the current user account, including the plan type, used quotas, and billing period.
—AccountInfo
Analysis: General NLU processing
POST /v3/analysisThe primary endpoint for NLU. Performs one or more requested analyses (entities, tags, sentiment, etc.) on the input text.
RequestResponse
GET /v3/analysisA simplified GET version of the analysis endpoint where text and parameters are passed as query arguments.
query parametersResponse
POST /v3/analysis/batchSubmits a list of documents for analysis in a single request.
BatchRequestList[Response]
Specialized Analyses: Shortcut endpoints
POST /v3/entitiesShortcut endpoint specifically for named and general entity recognition.
RequestResponse
POST /v3/tagsShortcut endpoint specifically for semantic tagging and categorization.
RequestResponse
POST /v3/sentimentShortcut endpoint specifically for document and item-level sentiment analysis.
RequestResponse
POST /v3/languageShortcut endpoint specifically for language detection.
RequestResponse
POST /v3/relationsShortcut endpoint specifically for relation and dependency analysis.
RequestResponse
POST /v3/correctionPerforms spelling and diacritics correction on the input text.
RequestResponse

For full technical details, including interactive examples and schema definitions, please refer to the Swagger Documentation.