> ## Documentation Index > Fetch the complete documentation index at: https://docs.textsetu.com/llms.txt > Use this file to discover all available pages before exploring further. # List glossary terms > Return a paginated page of the glossary's terms, each with its per-language translations. Combine the query params to search by text, filter by language, status, or usage, and sort. ## OpenAPI ````yaml /openapi/textsetu.json get /glossaries/{glossaryId}/terms openapi: 3.1.0 info: title: TextSetu API version: 1.2.0 description: >- Public REST API for TextSetu. Authenticate with a Personal Access Token (tsu_pat_…) or a project token (tsu_proj_…) via the `Authorization: Bearer ` header. **Authorization is permission-based.** Every token carries an explicit allow-list of RBAC permission keys (e.g. `translation_read`), and each endpoint declares the permission it requires (`x-permission`). A token's effective access is its underlying authority ∩ its allow-list — a PAT is further bounded by its owner's role-based permissions, so it can only narrow, never exceed, what the owner already has. A project token is bound to a single project. There are no coarse read/write/manage scopes. **Response envelope.** Every endpoint returns `{ "success": true, "data": … }` on success and `{ "success": false, "error": { "code", "message" } }` on failure. **Rate limit.** 600 requests/minute, keyed by token (or by IP when unauthenticated). Exceeding it returns 429 with the standard error envelope. servers: - url: https://api.textsetu.com/api/v1 description: Production - url: /api/v1 description: This server (self-hosted / same-origin) security: - bearerAuth: [] tags: - name: Projects description: >- Read project metadata — settings, key separator, and the approval/branching flags that shape how the other endpoints behave. - name: Languages description: >- List and manage a project's target languages. Each language is referenced by its BCP-47 code; the source language is flagged separately. - name: Translations description: >- Manage a project's translations: create, read, update, and delete translation keys — the identifiers your app looks up, carrying metadata (description, tags, screenshot) — and set the translated value for a key in a given language. Value writes honor the project's approval workflow — non-approver writes land as `pending_review`. - name: Stats description: >- Per-language completeness and approval progress for a project — the numbers behind the dashboard. - name: Import/Export description: >- Bulk-load source files into a project or export the current translations. Supports the same file formats as the web app. - name: Branches description: >- Work on translations in isolation and merge them back. Branch reads/writes mirror the main endpoints but stage changes as a diff until merge. See the [branching guide](/docs/guides/branches). - name: Glossary description: >- Manage term bases — approved terminology and its translations — and check a string against them. See the [glossary guide](/docs/guides/glossary). - name: Translation Memory description: >- Reusable translation stores. Fuzzy-match and concordance-search prior translations to reuse them. See the [translation memory guide](/docs/guides/translation-memory). - name: AI description: >- Machine-translate a project with the org's configured AI engine (brand voice, glossary/TM grounding, and an optional review pass). Runs asynchronously — start a run and poll the returned `jobId`. - name: Webhooks description: >- Get notified when a project's translations change, instead of polling. Register an HTTPS endpoint, subscribe it to the events you care about, and TextSetu POSTs a signed payload whenever one occurs. Payloads follow the [Standard Webhooks](https://www.standardwebhooks.com) spec — verify the `webhook-signature` header with any compatible library. Delivery is at-least-once and unordered, so treat `webhook-id` as an idempotency key. Failed deliveries are retried five times over roughly seven hours, and every attempt is inspectable and replayable via the delivery log. - name: Meta description: Service-level and cross-cutting endpoints. paths: /glossaries/{glossaryId}/terms: get: tags: - Glossary summary: List glossary terms description: >- Return a paginated page of the glossary's terms, each with its per-language translations. Combine the query params to search by text, filter by language, status, or usage, and sort. parameters: - name: glossaryId in: path required: true schema: type: string description: Glossary id (UUID) or id-embedded path slug. - name: page in: query description: 1-based page number. schema: default: 1 type: integer minimum: 1 - name: limit in: query description: Terms per page (max 200). schema: default: 50 type: integer minimum: 1 maximum: 200 - name: search in: query description: Substring match on the term text. schema: type: string - name: language in: query description: Only terms having a translation in this language code. schema: type: string - name: status in: query description: Filter by translation status. schema: type: string enum: - approved - pending_review - draft - name: usageStatus in: query description: Filter by preferred / deprecated / forbidden. schema: type: string enum: - preferred - deprecated - forbidden - name: doNotTranslate in: query description: Only do-not-translate terms when true. schema: anyOf: - type: boolean - type: string enum: - 'true' - 'false' - name: caseSensitive in: query description: Only case-sensitive terms when true. schema: anyOf: - type: boolean - type: string enum: - 'true' - 'false' - name: sort in: query description: Sort field. schema: default: term type: string enum: - term - createdAt - updatedAt - name: order in: query description: Sort direction. schema: default: asc type: string enum: - asc - desc responses: '200': description: A page of terms with their per-language translations. content: application/json: schema: type: object required: - success - data properties: success: type: boolean const: true data: type: object properties: terms: type: array items: type: object properties: id: type: string description: Unique term id (UUID). examples: - a1b2c3d4-0000-4000-8000-000000000020 glossaryId: type: string description: Id of the glossary this term belongs to. examples: - a1b2c3d4-0000-4000-8000-000000000010 term: type: string description: The source-language term. examples: - Sign in doNotTranslate: type: boolean description: True when the term must be left untranslated. examples: - false caseSensitive: type: boolean description: >- True when matching respects the term's exact casing. examples: - false usageStatus: type: string description: >- Usage rule: `preferred`, `deprecated`, or `forbidden`. examples: - preferred notes: anyOf: - type: string - type: 'null' description: Optional translator guidance, or `null`. examples: - >- Use the verb form; never capitalize mid-sentence. createdAt: type: string description: Creation timestamp (ISO 8601). examples: - '2026-01-15T09:24:00.000Z' updatedAt: type: string description: Last-update timestamp (ISO 8601). examples: - '2026-02-02T14:05:00.000Z' translations: type: array items: type: object properties: languageCode: type: string description: >- BCP-47 language code this translation is written in. examples: - fr value: type: string description: >- The approved (or current) translation of the term. examples: - Se connecter status: type: string description: >- Review state: `approved`, `pending_review`, or `draft`. examples: - approved approvedAt: anyOf: - type: string - type: 'null' description: >- When the translation was approved (ISO 8601), or `null` if not approved. examples: - '2026-01-16T11:00:00.000Z' proposedValue: anyOf: - type: string - type: 'null' description: >- A pending proposal awaiting approval, or `null` when there is none. examples: - null required: - languageCode - value - status - approvedAt - proposedValue additionalProperties: false description: Per-language translations of the term. required: - id - glossaryId - term - doNotTranslate - caseSensitive - usageStatus - notes - createdAt - updatedAt - translations additionalProperties: false total: type: integer description: >- Total number of terms matching the query across all pages. examples: - 128 page: type: integer description: 1-based page number of this result. examples: - 1 limit: type: integer description: Maximum terms returned per page. examples: - 50 required: - terms - total - page - limit additionalProperties: false components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- API token: tsu_pat_… (PAT) or tsu_proj_… (project token). The token's granted RBAC permissions determine access; see each operation's `x-permission`. ````