Overview

ELI is a Natural Language Processing API specifically designed for the Thai language, offering tools like word segmentation, part-of-speech tagging, and named entity recognition. It fills a gap for developers building Thai-language applications that need linguistic analysis. An API key is required and requests are made via standard HTTP POST calls.

Beginner Tip

Thai text requires proper UTF-8 encoding — always set Content-Type to application/json with charset=utf-8 to prevent garbled characters in both your request and the response.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

translated text
source language
target language
confidence score

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "status": "success",
  "data": {
    "result": "Data from ELI",
    "description": "Natural Language Processing Tools for Thai Language",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

words List of segmented Thai word tokens extracted from the input text
pos_tags Part-of-speech tags corresponding to each word in the words array
entities Named entities detected in the text, such as person names or locations

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://nlp.insightera.co.th/docs/";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

401 Unauthorized API key not included or incorrectly formatted in the Authorization header
Pass the key as "Authorization: Bearer YOUR_API_KEY" in every request header
Garbled Thai characters in response Response not decoded as UTF-8 by the client
Ensure your HTTP client reads the response body with UTF-8 encoding explicitly set
400 Bad Request on empty text Sending an empty or whitespace-only string as input
Validate that the text field contains actual Thai content before sending the request

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS UNKNOWN
Category Text Analysis
Difficulty Intermediate
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →