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

# Get context



## OpenAPI

````yaml /openapi.yaml get /reason/context
openapi: 3.1.0
info:
  title: Automatic Rostering API
  version: 2.0.0
  description: >-
    Automatic Rostering acts as the modern intelligence layer for your workforce
    management product.
  license:
    name: Proprietary
servers:
  - url: https://api-stage.automaticrostering.visma.net
    description: Stage environment
  - url: https://api.automaticrostering.visma.net
    description: Production environment
security:
  - vismaConnectBearer: []
tags:
  - name: Roster
    description: Submit, monitor, stop, and fetch roster jobs.
  - name: Reason
    description: Configure integrator context used by Reasoning Engine capabilities.
paths:
  /reason/context:
    get:
      tags:
        - Reason
      summary: Get context
      operationId: getReasoningContext
      responses:
        '200':
          $ref: '#/components/responses/ReasoningContext'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  responses:
    ReasoningContext:
      description: >-
        The authenticated integrator's Reasoning Context, or an empty context
        when none is stored.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ReasoningContext'
    InternalServerError:
      description: Server failed to process the request.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    ReasoningContext:
      type: object
      description: >-
        Integrator-owned guidance for Reasoning Engine capabilities. The
        complete JSON document must not exceed 16 KiB.
      additionalProperties: false
      required:
        - terminology
        - ruleLabelDescriptions
        - customInstructions
      properties:
        terminology:
          type: object
          description: >-
            Preferred terms used in generated partner-facing messages, grouped
            by Output Language.
          additionalProperties: false
          properties:
            en:
              $ref: '#/components/schemas/Terminology'
            nb:
              $ref: '#/components/schemas/Terminology'
            nl:
              $ref: '#/components/schemas/Terminology'
            sv:
              $ref: '#/components/schemas/Terminology'
            lv:
              $ref: '#/components/schemas/Terminology'
        ruleLabelDescriptions:
          type: object
          description: >-
            Guidance keyed by exact, case-sensitive rule label. Values may be
            written in any language.
          additionalProperties:
            type: string
            minLength: 1
        customInstructions:
          type: array
          description: >-
            Free-form guidance available to Reasoning Engine capabilities,
            expressed as individual instructions in any language. A terminology
            exception applies only when it explicitly names the selected Output
            Language.
          items:
            type: string
            minLength: 1
    Error:
      type: object
      additionalProperties: false
      required:
        - code
        - message
      properties:
        code:
          type: string
        message:
          type: string
    Terminology:
      type: object
      additionalProperties: false
      description: >-
        Preferred base terms for one Output Language. Generated text may
        inflect, pluralize, or capitalize them for grammar.
      properties:
        employee:
          type: string
          minLength: 1
          description: Preferred base term for an employee.
        shift:
          type: string
          minLength: 1
          description: Preferred base term for a shift.
  securitySchemes:
    vismaConnectBearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Include the access token in the Authorization header using the Bearer
        scheme.

````