> ## 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.

# Set Feature

> Set an operator preference on a feature the market leaves open.

Refuses, citing the legal basis, when the resolved market profile forbids or
requires the feature. That refusal is evidence in itself: it shows the
platform enforced a jurisdictional boundary rather than merely describing one.

**Who may call it:** governance-officer or admin. A workspace API key is refused here: this is an act that belongs to a named person.



## OpenAPI

````yaml /api/openapi.json put /v1/features/{feature_key}
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/features/{feature_key}:
    put:
      tags:
        - Market
      summary: Set Feature
      description: >-
        Set an operator preference on a feature the market leaves open.


        Refuses, citing the legal basis, when the resolved market profile
        forbids or

        requires the feature. That refusal is evidence in itself: it shows the

        platform enforced a jurisdictional boundary rather than merely
        describing one.


        **Who may call it:** governance-officer or admin. A workspace API key is
        refused here: this is an act that belongs to a named person.
      operationId: set_feature_v1_features__feature_key__put
      parameters:
        - name: feature_key
          in: path
          required: true
          schema:
            type: string
            title: Feature Key
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FeatureSet'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FeatureSetOut'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - bearerToken: []
components:
  schemas:
    FeatureSet:
      properties:
        enabled:
          type: boolean
          title: Enabled
        reason:
          type: string
          maxLength: 500
          minLength: 1
          title: Reason
      type: object
      required:
        - enabled
        - reason
      title: FeatureSet
    FeatureSetOut:
      properties:
        feature:
          $ref: '#/components/schemas/FeatureRow'
        market_profile:
          type: string
          title: Market Profile
        set_by:
          type: string
          title: Set By
        reason:
          type: string
          title: Reason
        title:
          type: string
          title: Title
      type: object
      required:
        - feature
        - market_profile
        - set_by
        - reason
        - title
      title: FeatureSetOut
      description: The feature after the change, and who changed it.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    FeatureRow:
      properties:
        key:
          type: string
          title: Key
        title:
          type: string
          title: Title
        description:
          type: string
          title: Description
        category:
          type: string
          title: Category
        caution:
          anyOf:
            - type: string
            - type: 'null'
          title: Caution
        state:
          type: string
          title: State
        enabled:
          type: boolean
          title: Enabled
        source:
          type: string
          title: Source
        locked:
          type: boolean
          title: Locked
        legal_basis:
          anyOf:
            - type: string
            - type: 'null'
          title: Legal Basis
        market_profile:
          anyOf:
            - type: string
            - type: 'null'
          title: Market Profile
      type: object
      required:
        - key
        - title
        - description
        - category
        - caution
        - state
        - enabled
        - source
        - locked
        - legal_basis
        - market_profile
      title: FeatureRow
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  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.