How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Farasa Web API

Farasa ("insight") is the Arabic text-processing toolkit built by the Arabic Language Technologies group at QCRI, Hamad Bin Khalifa University, and offered free to registered users as a keyed web API. Six endpoints were confirmed live on 2026-08-30 by unauthenticated POST probes — segmentation, lemmatization, pos, ner, diacritize and spellcheck each returned 400 "invalid api key", while sibling module paths returned 404. The api_key travels in the request body rather than a header. No OpenAPI is published by the provider; the definition in this repo is DERIVED from QCRI's own Python/Java/JavaScript/curl samples plus those probes, and the success payload shape is deliberately left unasserted because it could not be observed.

Farasa Web API is one of 5 APIs that Hamad Bin Khalifa University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Natural Language Processing, Arabic, and Research. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 6 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://farasa.qcri.org/webapi.

6 operations 6 paths 1 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://farasa.qcri.org/webapi
Resource Areas
1

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 POST. Each is listed below with its method, path, parameters, and response codes.

Arabic NLP 6

Arabic language processing modules.

POST
/segmentation/
Segment Arabic text into clitics and stems
farasaSegmentation body → 200400
POST
/lemmatization/
Reduce Arabic tokens to their lemmas
farasaLemmatization body → 200400
POST
/pos/
Part-of-speech tag Arabic text
farasaPos body → 200400
POST
/ner/
Recognize named entities in Arabic text
farasaNer body → 200400
POST
/diacritize/
Restore diacritics on Arabic text
farasaDiacritize body → 200400
POST
/spellcheck/
Spell-check Arabic text
farasaSpellcheck body → 200400

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is FarasaRequest (2 properties). Each schema is shown below with its type and property counts.

FarasaRequest
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hbku-farasa-api-openapi.yml Raw ↑

Other APIs Hamad Bin Khalifa University publishes across the network.

Fanar API
Elmi Research Portal — OAI-PMH
HBKU Academic Catalog — Course Search
Manara — Qatar Research Repository (HBKU portal)
Where this information came from

This is an independent, third-party profile of Farasa Web API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.