@withmateza/sdk

Core Node client for the Mateza public API.

Use this package when you want the raw, framework-agnostic API client and typed response schemas for translation, speech, multimodal jobs, usage, request logs, glossary, language catalog, and feedback.

Install

npm install @withmateza/sdk
pnpm add @withmateza/sdk

These packages are published to the public npm registry. If you are consuming them from this monorepo, use the workspace package references already defined in pnpm-workspace.yaml.

Quick Start

import { createClient } from "@withmateza/sdk";

const mateza = createClient({
  baseUrl: "https://api.mateza.rw",
  apiKey: process.env.MATEZA_API_KEY,
});

const result = await mateza.translate({
  text: "Hello world",
  source_lang: "en",
  target_lang: "rw",
});

console.log(result.data.translation);

If you are calling the API from a browser or native client, use createPublicClient and a client key instead of a server API key.

API Overview

Exported entry points:

• createClient and createPublicClient
• ApiError, request, ClientOptions, and FetchFn
• language-catalog, model-exposure, and schemas exports

Main methods on the client:

• translate
• translateBatch
• startSpeechTranslate
• processMultimodal
• getSpeechJob
• waitForSpeechJob
• createTranslationFeedback
• listTranslationFeedback
• getUsage
• listRequests
• listGlossary
• listLanguages
• guide
• uploadMedia
• getUploadedMedia

Auth and Config

• Set baseUrl to the Mateza API host, for example https://api.mateza.rw.
• Use apiKey for server-side requests.
• Use clientKey for browser-safe requests.
• You can override credentials per call with api_key or client_key.
• createPublicClient is an alias of createClient.

Common Mistakes

• Passing a server API key into browser code.
• Forgetting to set baseUrl.
• Importing from internal source files instead of the package entry point.
• Assuming the response is untyped JSON. The client parses responses through the published schemas.

See the shared getting-started guide in docs/package-getting-started.md for end-to-end examples.

API docs: https://api.mateza.rw/docs

API endpoint: https://api.mateza.rw