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

# Disable the gate for the environment

> Disables the specified gate for the environment.



## OpenAPI

````yaml put /environments/{environmentId}/gates/{gateId}/disable
openapi: 3.0.1
info:
  title: Dashboard API
  description: Dashboard API documentation
  version: 1.0.0
servers:
  - url: https://app.dynamicauth.com/api/v0
  - url: https://app.dynamic.xyz/api/v0
  - url: http://localhost:3333/api/v0
security: []
tags:
  - name: Analytics
  - name: SDK
  - name: Organizations
  - name: Projects
  - name: Environments
  - name: Users
  - name: Invites
  - name: Tokens
  - name: Origins
  - name: Allowlists
  - name: Wallets
  - name: Members
  - name: Sessions
  - name: Settings
  - name: Gates
  - name: Chains
  - name: Exports
  - name: Events
  - name: Webhooks
  - name: Custom Fields
  - name: OrganizationMfaSettings
  - name: CustomHostnames
  - name: TestAccount
  - name: NameServices
  - name: GlobalWallets
  - name: GlobalWalletConnections
  - name: UserApiTokens
  - name: Waas
  - name: WalletConnect
paths:
  /environments/{environmentId}/gates/{gateId}/disable:
    put:
      tags:
        - Gates
      summary: Disable the gate for the environment
      operationId: disableGate
      parameters:
        - $ref: '#/components/parameters/environmentId'
        - $ref: '#/components/parameters/gateId'
      responses:
        '200':
          description: Successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Gate'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '500':
          $ref: '#/components/responses/InternalServerError'
      security:
        - bearerAuth: []
components:
  parameters:
    environmentId:
      in: path
      name: environmentId
      required: true
      description: ID of the environment
      schema:
        $ref: '#/components/schemas/uuid'
    gateId:
      in: path
      name: gateId
      required: true
      description: ID of the gate
      schema:
        $ref: '#/components/schemas/uuid'
  schemas:
    Gate:
      type: object
      required:
        - id
        - name
        - rules
        - outcome
      properties:
        id:
          $ref: '#/components/schemas/uuid'
        name:
          description: >-
            Human-readable name of the gate. This should be something helpful to
            organize gates.
          example: Super User Gate
          type: string
        scope:
          description: >-
            String for the resulting scope of the gate. If the rules of the gate
            apply to the user being verified, then this scope will be surfaced
            in the JWT. If a scope is not provided for the gate, the default
            behavior of the gate would be to block access to users that the
            rules do not currently apply to.
          example: superuser
          type: string
        enabledAt:
          type: string
          description: If the gate is enabled, then this timestamp will be present.
          format: date-time
          nullable: true
        rules:
          type: array
          description: >-
            The rules which will be used to evaluate users being verified. If
            multiple rules are present in a single gate, then all the rules need
            to apply for the user to gain the scope defined by the gate.
          items:
            $ref: '#/components/schemas/GateRule'
        outcome:
          $ref: '#/components/schemas/AccessOutcomeEnum'
    uuid:
      type: string
      pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
      minLength: 36
      maxLength: 36
      example: 95b11417-f18f-457f-8804-68e361f9164f
    GateRule:
      type: object
      description: >-
        Definition for a single rule in a Gate. This will check for the presence
        of a token or NFT, given the contract address, in the wallet of a user
        being evaluated. For multi-wallet users, we will check all wallets. If a
        filter is defined, then we will also check that the filter checks apply
        to the user
      required:
        - type
        - address
      properties:
        type:
          $ref: '#/components/schemas/GateRuleType'
        address:
          $ref: '#/components/schemas/TokenAddress'
        filter:
          $ref: '#/components/schemas/GateRuleFilter'
        chain:
          $ref: '#/components/schemas/ChainEnum'
    AccessOutcomeEnum:
      type: string
      enum:
        - scope
        - siteAccess
        - block
    Unauthorized:
      type: object
      properties:
        error:
          type: string
          example: No jwt provided!
    Forbidden:
      type: object
      properties:
        error:
          type: string
          example: Access Forbidden
    InternalServerError:
      type: object
      properties:
        error:
          type: string
          example: Internal Server Error
    GateRuleType:
      type: string
      enum:
        - nft
        - token
    TokenAddress:
      description: >-
        Defines one token address connected with network Id on which it's
        working
      type: object
      required:
        - networkId
        - contractAddress
      properties:
        networkId:
          description: Id of the network
          type: number
          example: 1
        contractAddress:
          $ref: '#/components/schemas/WalletPublicKey'
    GateRuleFilter:
      type: object
      description: Defines the filter properties used for the gate
      properties:
        tokenId:
          $ref: '#/components/schemas/OptionalHexString'
        amount:
          type: number
          description: >-
            Minimum token or NFT amount held by the user. If this `amount` field
            is provided, then Dynamic will also check that the user has this
            minimum amount held by the user of the NFT or Token
    ChainEnum:
      type: string
      enum:
        - ETH
        - EVM
        - FLOW
        - SOL
        - ALGO
        - STARK
        - COSMOS
        - BTC
        - ECLIPSE
        - SUI
        - SPARK
        - TRON
        - APTOS
        - TON
        - STELLAR
    WalletPublicKey:
      type: string
      pattern: ^[A-Za-z0-9]{18,100}$
      description: >-
        Valid blockchain wallet address, must be an alphanumeric string without
        any special characters
      example: '0xbF394748301603f18d953C90F0b087CBEC0E1834'
      maxLength: 255
    OptionalHexString:
      type: string
      pattern: ^$|^(0x|0X)[a-fA-F0-9]{1,40}$
      example: '0x01'
  responses:
    Unauthorized:
      description: Unauthorized
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Unauthorized'
    Forbidden:
      description: Forbidden
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Forbidden'
    InternalServerError:
      description: Internal Server Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/InternalServerError'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````