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

# Update counter

> Update counter name, location, or webhook URL.



## OpenAPI

````yaml /swagger.json put /merchant/api/v1/counters/{counterID}
openapi: 3.0.3
info:
  title: Merchant API
  description: >-
    API for merchants to create and manage payment intents, POS counters, and
    transaction history in the FEX Payment Platform. Authentication uses
    Keycloak JWT (human merchants via password flow, POS terminals via client
    credentials).
  version: 1.0.0
  contact:
    name: FEX Payments Platform
servers:
  - url: http://api-sandbox.fexpayments.com
    description: Merchant API sandbox server
security: []
tags:
  - name: Payment Intents
    description: Create and manage payment intents
  - name: Counters
    description: >-
      POS terminal (counter) management — each counter has its own Keycloak
      client credentials and webhook endpoint
  - name: Admin
    description: Back-office endpoints restricted to platform admin role (`admin`)
  - name: Public
    description: Public endpoints accessible without authentication (for QR code payments)
  - name: Onboarding
    description: Merchant registration — requires platform admin JWT (realm role `admin`)
paths:
  /merchant/api/v1/counters/{counterID}:
    put:
      tags:
        - Counters
      summary: Update counter
      description: Update counter name, location, or webhook URL.
      parameters:
        - name: counterID
          in: path
          required: true
          description: Counter ID
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateCounterRequest'
      responses:
        '200':
          description: Counter updated
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  counter:
                    $ref: '#/components/schemas/Counter'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
      security:
        - BearerAuth: []
components:
  schemas:
    UpdateCounterRequest:
      type: object
      description: All fields are optional — only provided fields are updated
      properties:
        name:
          type: string
          example: Counter 1 (updated)
        location:
          type: string
          example: Ground Floor, Register 1
        webhook_url:
          type: string
          format: uri
          example: https://pos.example.com/webhooks/v2/payments
    Counter:
      type: object
      description: A POS terminal belonging to a merchant
      properties:
        id:
          type: string
          format: uuid
          example: c1d2e3f4-a5b6-7890-abcd-ef1234567890
        merchant_id:
          type: string
          format: uuid
          example: 74815c83-e47b-4dc5-aefe-abe4484dd280
        name:
          type: string
          example: Counter 1
        location:
          type: string
          example: Floor 2, Register 3
        keycloak_client_id:
          type: string
          description: >-
            Keycloak client ID for this counter (for reference; secret not
            shown)
          example: counter-c1d2e3f4-a5b6-7890-abcd-ef1234567890
        webhook_url:
          type: string
          format: uri
          example: https://pos.example.com/webhooks/payments
        status:
          type: string
          enum:
            - active
            - inactive
          example: active
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
      required:
        - id
        - merchant_id
        - name
        - status
    ErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
          example: Invalid request body
      required:
        - success
        - error
  responses:
    BadRequest:
      description: Bad request — invalid input
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error: Amount must be greater than 0
    Unauthorized:
      description: Unauthorized — missing or invalid JWT
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error: Unauthorized
    NotFound:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error: Payment intent not found
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Keycloak JWT. Roles: `admin` (platform admin — can register merchants,
        act on behalf of any merchant), `merchant` (dashboard user — scoped to
        their own `merchant_id` via user attribute mapper), POS terminals use
        client credentials flow with `merchant_id` injected via protocol mapper.

````