Quenza ShowClient API

The ShowClient API from Quenza — 1 operation(s) for showclient.

OpenAPI Specification

quenza-showclient-api-openapi.yml Raw ↑
openapi: 3.1.0
info:
  title: Quenza ArchiveClient ShowClient API
  version: 1.0.0
  description: The Quenza API allows you to integrate your systems with Quenza — manage clients, sync data, and automate workflows. Authenticate using a Bearer token from your workspace settings under Developer Tools → API Token.
servers:
- url: https://developers.quenza.com/v1
security:
- http: []
tags:
- name: ShowClient
paths:
  /clients/{client}:
    get:
      operationId: developers.v1.clients.show
      description: Returns a single client by their ID.
      summary: Get a client
      tags:
      - ShowClient
      parameters:
      - name: client
        in: path
        required: true
        description: The client sqid
        schema:
          type: integer
      responses:
        '200':
          description: '`ClientResource`'
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/ClientResource'
                required:
                - data
        '404':
          $ref: '#/components/responses/ModelNotFoundException'
        '401':
          $ref: '#/components/responses/AuthenticationException'
components:
  responses:
    ModelNotFoundException:
      description: Not found
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
                description: Error overview.
            required:
            - message
    AuthenticationException:
      description: Unauthenticated
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
                description: Error overview.
            required:
            - message
  schemas:
    ClientResource:
      type: object
      properties:
        id:
          type: string
        email:
          type: string
        first_name:
          type: string
        last_name:
          type: string
        status:
          $ref: '#/components/schemas/ClientStatus'
        is_guest:
          type: string
        timezone:
          type: string
        phone:
          type:
          - string
          - 'null'
        gender:
          type: string
        gender_identity:
          type:
          - string
          - 'null'
        birthdate:
          type: string
        invited_at:
          type: string
        invitation_accepted_at:
          type: string
        archived_at:
          type: string
        created_at:
          type: string
        updated_at:
          type: string
      required:
      - id
      - email
      - first_name
      - last_name
      - status
      - is_guest
      - timezone
      - phone
      - gender
      - gender_identity
      - birthdate
      - invited_at
      - invitation_accepted_at
      - archived_at
      - created_at
      - updated_at
      title: ClientResource
    ClientStatus:
      type: string
      enum:
      - active
      - pending
      - archived
      title: ClientStatus
  securitySchemes:
    http:
      type: http
      description: 'Authenticate using a **Bearer token** in the `Authorization` header:


        ```

        Authorization: Bearer {your-token}

        ```


        You can generate or regenerate your API token in your Quenza workspace under

        **Settings → Developer Tools → API Token**.'
      scheme: bearer