🔌 About This API

Integrate XOBDO's language data into your applications

The XOBDO API provides programmatic access to our comprehensive dictionary and linguistic resources. Use our RESTful endpoints to fetch word definitions, translations, language data, and more. All responses are returned in JSON format for easy integration.

🚀 Getting Started

Our API is currently open and doesn't require authentication for basic usage. Simply make HTTP requests to our endpoints and start accessing linguistic data immediately.

📊 Available Endpoints

RESTful endpoints for accessing dictionary data

`GET /api/words`

Retrieve a list of words with their definitions and translations

Parameters: limit, offset, language, search

`GET /api/words/{id}`

Get detailed information for a specific word by ID

Returns: Word details, definitions, translations, examples

`GET /api/languages`

List all supported languages in the XOBDO dictionary

Returns: Language codes, names, and metadata

`GET /api/search`

Search for words across multiple languages

Parameters: q (query), lang, fuzzy

💡 Usage Examples

Sample requests and responses

Search for a word

# Example request
curl
"https://xobdo.org/api/search?q=hello&lang=en"

This will search for the word "hello" in English and return matching entries with translations.

Get word details

# Example request
curl
"https://xobdo.org/api/words/12345"

Retrieve detailed information for word ID 12345, including all translations and usage examples.

📄 Response Format

Understanding API responses

All API responses are returned in JSON format with consistent structure:

{

  "status": "success",

  "data": {

    "words": [

      {

        "id": 12345,

        "word": "নমস্কাৰ",

        "language": "Assamese",

        "translations": ["hello", "greetings"]

      }

    ]

  },

  "meta": {

    "total": 1,

    "page": 1

  }

}

⚡ Usage Guidelines

Best practices and limitations

📊 Rate Limits

Currently no strict rate limits are enforced, but please be respectful and avoid excessive requests. We reserve the right to implement rate limiting for fair usage.

🔄 Caching

Consider implementing client-side caching for better performance. Dictionary data doesn't change frequently.

📧 Support

For API support or feature requests, please contact us at [email protected].