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

# Bulk update node access rules status with the Chainstack Platform API v2

> Activate or deactivate every access rule on a node in one request using the Chainstack Platform API v2. Send a POST request to /v2/nodes/{node_id}/access-rules/bulk-update-status/.



## OpenAPI

````yaml post /v2/nodes/{node_id}/access-rules/bulk-update-status/
openapi: 3.0.3
info:
  x-logo:
    url: https://chainstack.com/assets/docs/api-docs-logo.svg
    backgroundColor: '#F5F8FC'
    altText: Chainstack
  title: 💙 CHAINSTACK PLATFORM API
  version: v2
  contact:
    name: API Support
    email: support@chainstack.com
  description: >
    A set of API endpoints to operate and manage the platform resources.<br>

    See also a [quick API
    tutorial](https://docs.chainstack.com/reference/quick-tutorial).
servers:
  - url: https://api.chainstack.com
    description: API endpoint
security: []
paths:
  /v2/nodes/{node_id}/access-rules/bulk-update-status/:
    parameters:
      - $ref: '#/components/parameters/NodeIdPath'
    post:
      tags:
        - Node access rules V2
      summary: Bulk update node access rules status
      description: >
        Activate or deactivate every access rule on a node in one request.

        <br> Deactivating all rules lifts the restriction: the node endpoints
        then accept requests from any IP address and origin, subject to the
        endpoint authentication.
      operationId: bulkUpdateNodeAccessRulesStatusV2
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/NodeAccessRulesBulkStatusV2'
            examples:
              activate:
                summary: Activate all rules
                value:
                  status: activated
        required: true
      responses:
        '200':
          description: >-
            All access rules on the node now have the requested status. No
            response body.
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '404':
          $ref: '#/components/responses/NotFoundError'
      security:
        - APIKeyAuthentication: []
components:
  parameters:
    NodeIdPath:
      name: node_id
      in: path
      required: true
      description: ID of the node.
      schema:
        type: string
        example: ND-123-456-789
  schemas:
    NodeAccessRulesBulkStatusV2:
      type: object
      required:
        - status
      properties:
        status:
          type: string
          enum:
            - activated
            - deactivated
          description: The status to set on every access rule on the node.
  responses:
    ValidationError:
      description: Validation error.
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: object
                properties:
                  code:
                    type: string
                    description: A string indicating the kind of error.
                  message:
                    type: string
                    description: A human-readable description of the error.
                  fields:
                    type: object
                    additionalProperties:
                      type: array
                      items:
                        type: string
                    description: Optional. Field-level validation errors.
    UnauthorizedError:
      description: Authentication credentials were missing or incorrect.
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: object
                properties:
                  code:
                    type: string
                    description: A string indicating the kind of error.
                  message:
                    type: string
                    description: A human-readable description of the error.
    ForbiddenError:
      description: The request is not allowed with the current permissions.
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: object
                properties:
                  code:
                    type: string
                    description: A string indicating the kind of error.
                  message:
                    type: string
                    description: A human-readable description of the error.
    NotFoundError:
      description: >-
        Object does not exist or caller has insufficient permissions to access
        it.
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: object
                properties:
                  code:
                    type: string
                    description: A string indicating the kind of error.
                  message:
                    type: string
                    description: A human-readable description of the error.
  securitySchemes:
    APIKeyAuthentication:
      type: http
      scheme: bearer
      description: >
        Chainstack API uses [API
        keys](https://docs.chainstack.com/reference/platform-api-getting-started)
        to authenticate requests. You can view and manage your API keys in the
        platform UI.

        Your API keys carry many privileges, so be sure to keep them secure!

        Provide your API key as the `Authorization` header. The value of the
        header consists of `Bearer` prefix and secret key generated through the
        platform UI.


        ```bash

        curl -X GET 'https://api.chainstack.com/v1/organization/' \

        --header 'Authorization: Bearer
        FX7CWlLg.FMpAO8cgCX2N7s41EncRru2nb5CmTZUt'

        ```


        All API requests must be made over HTTPS.

````