Docs/APIs/Text Lemmatizer

Text Lemmatizer

Lemmatize text

OperationalCredits 2 per callp50 468msText ProcessingStar

Overview

Lemmatizer parses `text` with the compromise natural-language library and asks it to compute a root for every term. compromise tags each word with its part of speech and uses that to find the dictionary form, which is why irregular forms such as "geese" and "went" resolve to "goose" and "go". Before parsing, the first tab, carriage return and line feed in the text are replaced with spaces and the text is trimmed.

For each term the normalized word is checked against a short stopword list (the, a, an, in, on, at, to, from, for, with, by, of), and those words are skipped. The root has any trailing possessive "'s" removed. Because compromise maps forms of "be", "have" and "do" inconsistently, the service applies its own table on top: is, am, are, was, were, been and being become `be`; has, had and having become `have`; does, did and done become `do`. Each resulting lemma is counted, and different surface forms of the same word add to the same count.

`lemmas` is an object keyed by lemma with an integer occurrence count as the value, and `found` is the number of keys. The object is capped at the first 50 distinct lemmas in the order they first appear; later ones are dropped and `found` reports the capped total. Words that are already in base form are included, and words compromise cannot resolve fall back to their normalized spelling, so some past-tense forms can appear unchanged. If no lemma is produced, the request returns a 404. On the Free plan `lemmas` is null and only `found` is returned.

Live Test Text Lemmatizer API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

POSThttps://api.apiverve.com/v1/lemmatizer
curl -X POST https://api.apiverve.com/v1/lemmatizer \
  -H "x-api-key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "The cats ran from door to door"
}'

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
textRequiredstringThe text to lemmatize

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "found": 3,
    "lemmas": {
      "cat": 1,
      "ran": 1,
      "door": 2
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
foundnumber3The number of lemmas found in the input text
lemmasPremiumobject{...}Each dictionary base form found in the text, mapped to how many times it occurs: "dogs" and "dog" both count toward dog, "went" toward go
catPremiumnumber1
ranPremiumnumber1
doorPremiumnumber2

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Search Query Normalization
Search engines convert user queries into root words to match plural or conjugated variations against indexed product titles.
Customer Feedback Clustering
Group incoming support tickets by topic after reducing verbs and nouns to base forms for cleaner text classification.
Vocabulary Learning Systems
Language learning platforms detect inflected verb forms across reading exercises and map them back to headwords in student flashcards.
SEO Content Auditing
Before scanning articles for keyword density, content marketing platforms strip grammatical suffixes to measure true term frequencies across drafts.

Other ways to use Text Lemmatizer

Set up Text Lemmatizer on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Text Processing:

Was this page helpful?