> ## Documentation Index
> Fetch the complete documentation index at: https://docs.judit.io/llms.txt
> Use this file to discover all available pages before exploring further.

# List supported courts

> Lists every court covered by Miner with tribunal_id and acronym, sorted by acronym. Use it to discover the IDs accepted by the tribunals filter.



## OpenAPI

````yaml openapi/miner.yaml GET /tribunals
openapi: 3.0.3
info:
  title: Judit Miner API — Requests, responses & tribunals
  description: >
    OpenAPI description for miner API routes that manage lawsuit search
    **requests**

    (count, create, status), paginated **responses** (lawsuit results), and the

    **tribunals** reference list (ids used in request filters).


    - `company_id` and `user_id` are **not** sent by the client on `POST
    /requests/create`;
      the server fills them from the authenticated session.
    - On `POST /requests/count`, the server merges `company_id` and `user_id`
    from context
      first; clients should send only filter fields (see request body schema).
    - Request and response bodies use **JSON**. Date-time fields are ISO 8601
    strings.

    - Count/create bodies are validated with a **strict** object (unknown keys
    are rejected).


    Authentication and `miner_enabled` behavior are enforced by
    `@judit-io/server`

    (e.g. JWT / gateway); this spec requires an API key provided in the
    `api-key` header.
  version: 1.0.0
servers:
  - url: https://miner.production.judit.io
    description: Production server
security:
  - ApiKeyAuth: []
tags:
  - name: Requests
    description: Create and inspect lawsuit search requests
  - name: Responses
    description: Paginated lawsuit results for a completed find request
  - name: Tribunals
    description: Reference data for tribunal identifiers used in filters
paths:
  /tribunals:
    get:
      tags:
        - Tribunals
      summary: List tribunals (id and acronym)
      description: >
        Returns all tribunals from persistence, ordered by **acronym**
        ascending.

        Each item’s `name` field is the tribunal **acronym**
        (`TypeormTribunal.acronym`),

        suitable for display and for cross-checking `tribunals` arrays in
        request filters.


        Registered with `miner_enabled: true` like the request/response routes.
      operationId: getTribunals
      responses:
        '200':
          description: Ordered list of tribunals
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TribunalNamesList'
components:
  schemas:
    TribunalNamesList:
      type: array
      items:
        $ref: '#/components/schemas/TribunalNameEntry'
    TribunalNameEntry:
      type: object
      required:
        - tribunal_id
        - name
      properties:
        tribunal_id:
          type: integer
          description: Identifier used in `tribunals` on count/create filters
        name:
          type: string
          description: Tribunal acronym (from `TypeormTribunal.acronym`)
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: api-key
      description: >-
        Replace with the actual API key requirement for your Miner API
        deployment.

````