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

# Configure a connector (connecteur, intégration)

> MERGES the submitted `config` patch into the connector's stored config and returns the connector (secrets re-masked). Only the fields you send are touched; omitted fields are left as they were. A field set to the mask sentinel (`••••••`) is SKIPPED — echoing a masked secret back keeps the stored one, so you never overwrite a credential you were never shown; send a real value only to change it. This operation STORES CREDENTIALS and can wire a LIVE external integration (it is the domain's lowest agent tier): do not call it speculatively, and confirm the credentials with the operator first. 404 on an unknown key, 400 on a malformed config (a nested/non-primitive value). Requires `pos.settings.manage`.



## OpenAPI

````yaml /openapi.json put /v1/integrations/{key}
openapi: 3.0.3
info:
  title: Solya POS API
  version: 1.0.0
  description: >-
    The Solya POS backend HTTP surface. Every documented operation is
    agent-ready: it carries an `operationId`, an agent-facing `description`, the
    `pos.*` scopes it enforces (`x-required-permissions`) and an `x-agent-tier`.
    Success responses return the payload as raw JSON; failures return the
    `ErrorResponse` envelope (`{ error: { code, message, statusCode } }`).
servers:
  - url: /
    description: The backend, relative to its deployed origin.
security: []
paths:
  /v1/integrations/{key}:
    put:
      tags:
        - Integrations
      summary: Configure a connector (connecteur, intégration)
      description: >-
        MERGES the submitted `config` patch into the connector's stored config
        and returns the connector (secrets re-masked). Only the fields you send
        are touched; omitted fields are left as they were. A field set to the
        mask sentinel (`••••••`) is SKIPPED — echoing a masked secret back keeps
        the stored one, so you never overwrite a credential you were never
        shown; send a real value only to change it. This operation STORES
        CREDENTIALS and can wire a LIVE external integration (it is the domain's
        lowest agent tier): do not call it speculatively, and confirm the
        credentials with the operator first. 404 on an unknown key, 400 on a
        malformed config (a nested/non-primitive value). Requires
        `pos.settings.manage`.
      operationId: updateIntegrationConfig
      parameters:
        - schema:
            type: string
            minLength: 1
          in: path
          name: key
          required: true
          description: >-
            The connector's stable key, e.g. `shopify` (from the connector
            list).
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                config:
                  type: object
                  additionalProperties:
                    anyOf:
                      - type: boolean
                      - type: string
                  description: >-
                    The config PATCH to merge; a field left at the `••••••` mask
                    sentinel is skipped.
              required:
                - config
              example:
                config:
                  shopDomain: new-shop.myshopify.com
                  accessToken: shpat_live_realsecret
      responses:
        '200':
          description: The connector as persisted (secrets masked).
          content:
            application/json:
              schema:
                type: object
                properties:
                  key:
                    type: string
                    minLength: 1
                  name:
                    type: string
                    minLength: 1
                  category:
                    type: string
                    enum:
                      - payment
                      - ecommerce
                      - accounting
                      - merchandising
                  enabled:
                    type: boolean
                  config:
                    type: object
                    additionalProperties:
                      anyOf:
                        - type: boolean
                        - type: string
                required:
                  - key
                  - name
                  - category
                  - enabled
                  - config
                additionalProperties: false
                description: The connector as persisted (secrets masked).
                example:
                  key: shopify
                  name: Shopify
                  category: ecommerce
                  enabled: true
                  config:
                    shopDomain: acme.myshopify.com
                    accessToken: ••••••
                    syncStock: true
        '400':
          description: >-
            The request failed schema validation; `error.fieldErrors` lists the
            fields.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationErrorResponse'
        '401':
          description: No valid credential was presented — send a bearer token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: The actor is authenticated but lacks the required `pos.*` scope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: No resource matches the addressed identifier.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: An unexpected server error — safe to retry idempotent requests.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    ValidationErrorResponse:
      type: object
      required:
        - error
      additionalProperties: false
      description: >-
        A `VALIDATION_FAILED` envelope carrying the offending fields in
        `fieldErrors`.
      properties:
        error:
          type: object
          required:
            - code
            - message
            - statusCode
          additionalProperties: false
          properties:
            code:
              type: string
              enum:
                - VALIDATION_FAILED
            message:
              type: string
            statusCode:
              type: integer
            fieldErrors:
              type: array
              description: >-
                One entry per rejected field: the field path and why it was
                rejected.
              items:
                type: object
                required:
                  - field
                  - message
                additionalProperties: false
                properties:
                  field:
                    type: string
                    description: Dot-path of the offending field.
                  message:
                    type: string
                    description: Why the field was rejected.
    ErrorResponse:
      type: object
      required:
        - error
      additionalProperties: false
      description: The uniform failure envelope every non-2xx response returns.
      properties:
        error:
          type: object
          required:
            - code
            - message
            - statusCode
          additionalProperties: false
          properties:
            code:
              type: string
              enum:
                - VALIDATION_FAILED
                - UNAUTHORIZED
                - FORBIDDEN
                - NOT_FOUND
                - CONFLICT
                - BUSINESS_RULE_VIOLATION
                - INTERNAL_ERROR
              description: >-
                Machine-readable kernel `ResultCode` — branch on this, not on
                `message`.
            message:
              type: string
              description: >-
                Human-readable explanation. Safe to surface; never leaks server
                internals.
            statusCode:
              type: integer
              description: >-
                The HTTP status, mirrored into the body so a client need not
                read headers.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        `Authorization: Bearer <token>`. Accepts EITHER a Keycloak access token
        (scopes-in-token) OR an opaque POS session token; both resolve to the
        same `pos.*` scope vocabulary the route guards enforce.

````