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

# Controls

> Is what you think is running, running?

**Who may call it:** any role. A workspace API key is refused here: this is an act that belongs to a named person.



## OpenAPI

````yaml /api/openapi.json get /v1/controls
openapi: 3.1.0
info:
  title: RotaGrant API
  version: 0.1.0
  description: >-
    The HTTP API of a RotaGrant deployment, made from the product's own route
    definitions at the commit named in `x-rotascale-source`. Nothing here is
    written by hand.


    There is no shared endpoint. RotaGrant runs in your environment, and your
    deployment serves its own copy of this description at `/api/docs`. That copy
    is the authority on what your version has and which features are switched
    on; this one is the reference for one commit of the main line. The version
    is 0.1.0: routes and shapes can still change.


    Every route says who may call it. Most need a bearer token from the identity
    provider your deployment uses, held by a person with the role named. The
    routes an SDK calls also accept a workspace API key. A few are open, and say
    why.
servers:
  - url: https://{deployment}
    description: Your own deployment. There is no shared endpoint.
    variables:
      deployment:
        default: rotagrant.internal.example
        description: The host your deployment answers on.
security: []
paths:
  /v1/controls:
    get:
      tags:
        - Overview
      summary: Controls
      description: >-
        Is what you think is running, running?


        **Who may call it:** any role. A workspace API key is refused here: this
        is an act that belongs to a named person.
      operationId: controls_v1_controls_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ControlsOut'
      security:
        - bearerToken: []
components:
  schemas:
    ControlsOut:
      properties:
        state:
          type: string
          title: State
        window_hours:
          type: integer
          title: Window Hours
        checks:
          items:
            $ref: '#/components/schemas/ControlCheck'
          type: array
          title: Checks
      type: object
      required:
        - state
        - window_hours
        - checks
      title: ControlsOut
    ControlCheck:
      properties:
        key:
          type: string
          title: Key
        title:
          type: string
          title: Title
        state:
          type: string
          title: State
        detail:
          type: string
          title: Detail
        consequence:
          type: string
          title: Consequence
          default: ''
        facts:
          additionalProperties: true
          type: object
          title: Facts
      type: object
      required:
        - key
        - title
        - state
        - detail
      title: ControlCheck
      description: One control, and whether it is actually running.
  securitySchemes:
    bearerToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        A token from the identity provider your deployment federates with. It
        identifies a person; their roles in the workspace decide what they may
        do.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.