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

# Push Local Config

> Push replacement connections/filesystems maps to a connector box.



## OpenAPI

````yaml POST /orgs/{org_id}/connectors/{connector_id}/local-config
openapi: 3.1.0
info:
  title: Timbal Platform API
  description: Public API documentation for the Timbal platform
  license:
    name: ''
  version: 2.0.0
servers:
  - url: https://api.timbal.ai
    description: Production
  - url: https://api.dev.timbal.ai
    description: Development
security: []
tags:
  - name: ace
    description: Action Control Engine (ACE) operations
  - name: alarms
    description: Metric series and threshold alarms
  - name: analytics
    description: Org and project analytics
  - name: billing
    description: Subscriptions, usage, and payment-related operations
  - name: channels
    description: Delivery channels alarms notify through
  - name: content
    description: Re-sign stored content URLs
  - name: files
    description: File operations
  - name: iam
    description: IAM — actions, roles, users, and authorization introspection
  - name: k2
    description: Knowledge Bases v2 operations
  - name: orgs
    description: Organization operations
  - name: projects
    description: Project operations
  - name: runs
    description: Execution operations
  - name: templates
    description: Public project template catalog
  - name: users
    description: Authenticated user profile
paths:
  /orgs/{org_id}/connectors/{connector_id}/local-config:
    post:
      tags:
        - connectors
      summary: '`POST /orgs/{org_id}/connectors/{connector_id}/local-config`'
      description: Push replacement connections/filesystems maps to a connector box.
      operationId: handler
      parameters:
        - name: org_id
          in: path
          required: true
          schema:
            type: string
        - name: connector_id
          in: path
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/LocalConfigReq'
        required: true
      responses:
        '202':
          description: Config push dispatched
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LocalConfigRes'
        '400':
          description: Empty payload (neither map present)
        '403':
          description: Forbidden
        '404':
          description: Connector not found
        '422':
          description: 'Connector offline (`code: connector_offline`)'
      security:
        - bearer_auth: []
components:
  schemas:
    LocalConfigReq:
      type: object
      properties:
        connections:
          type: object
          description: >-
            `connection_ref` → connection object, same shape as the
            `connections`

            map in the connector's `config.json` (e.g. `{ "kind": "postgres",

            "dsn": "...", "query": "read" }`). When present, **replaces** the

            connector's whole local connections map. Absent = keep local.
        filesystems:
          type: object
          description: >-
            `filesystem_ref` → filesystem root object, same shape as the

            `filesystems` map in `config.json` (e.g. `{ "path": "/srv/exports"
            }`).

            When present, **replaces** the connector's whole local filesystems
            map.

            Absent = keep local.
    LocalConfigRes:
      type: object
      required:
        - dispatched
        - connections
        - filesystems
      properties:
        connections:
          type: boolean
          description: Which maps were included in the push.
        dispatched:
          type: boolean
          description: >-
            Always true on a 202 — the connector validates/acks asynchronously

            over the channel and restarts to apply; watch the fleet listing for
            it

            to reconnect.
        filesystems:
          type: boolean
  securitySchemes:
    bearer_auth:
      type: http
      scheme: bearer
      description: >-
        Timbal API key. Obtain your API key from the Timbal platform settings.
        See [Authentication](/api-reference/authentication) for more
        information.

````