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

# List Clients

> Retrieve a paginated list of all clients



## OpenAPI

````yaml GET /clients
openapi: 3.1.0
info:
  title: Contazen API
  version: 1.2.0
  description: >
    Build powerful integrations with the Contazen invoicing platform. The
    Contazen API is organized around REST, 

    has predictable resource-oriented URLs, accepts JSON request bodies, returns
    JSON-encoded responses, 

    and uses standard HTTP response codes, authentication, and verbs.


    ## Authentication

    The API uses Bearer token authentication. Include your API key in the
    Authorization header.


    ### Getting your API Key

    1. Log in to your Contazen account

    2. Navigate to Settings > API

    3. Generate or copy your API key (starts with `sk_live_` for production or
    `sk_test_` for testing)


    ### Using the API Key

    Include your API key in the Authorization header:

    ```

    Authorization: Bearer sk_live_YOUR_API_KEY

    ```


    ### Example Request with cURL

    ```bash

    curl --request GET \
      --url https://api.contazen.ro/v1/clients \
      --header 'Authorization: Bearer sk_live_YOUR_API_KEY' \
      --header 'Accept: application/json'
    ```


    ## Rate Limiting

    - 1000 requests per hour per API key

    - 100 create operations per minute per API key


    Rate limit information is included in response headers:

    - `X-RateLimit-Limit`: Maximum requests allowed

    - `X-RateLimit-Remaining`: Requests remaining

    - `X-RateLimit-Reset`: Reset time (Unix timestamp)


    ## Pagination

    All list endpoints return paginated results with the following format:

    ```json

    {
      "success": true,
      "data": {
        "object": "list",
        "data": [...],
        "has_more": true,
        "total": 245,
        "page": 1,
        "per_page": 50,
        "total_pages": 5
      },
      "meta": {
        "version": "v1",
        "request_id": "req_1a2b3c4d",
        "response_time": "23.45ms"
      }
    }

    ```


    ## Multi-Work-Point Access

    API keys belong to a specific work point but can access data from all work
    points

    within the same parent company.


    ## Error Handling

    The API uses conventional HTTP response codes to indicate success or
    failure. 

    In general: 2xx codes indicate success, 4xx codes indicate an error due to
    the 

    information provided, and 5xx codes indicate an error with Contazen's
    servers.


    ## Expanding Nested Objects

    Many endpoints support the `expand` parameter to include related objects in
    the response.

    This follows the Stripe API pattern. For example:

    - `expand[]=lines` - Include invoice line items

    - `expand[]=payments` - Include payment records

    - `expand[]=client` - Include full client object


    ## Localization

    The API supports multiple languages through:

    - `locale` query parameter (en, ro)

    - `Accept-Language` header

    - Default: English
  contact:
    name: Contazen Support
    email: support@contazen.ro
    url: https://contazen.ro
  license:
    name: Proprietary
    url: https://www.contazen.ro/termeni-si-conditii-de-utilizare/
servers:
  - url: https://api.contazen.ro/v1
    description: Production API server
security:
  - bearerAuth: []
tags:
  - name: Authentication
    description: API authentication and test endpoints
  - name: Clients
    description: Manage your customers (B2B and B2C)
  - name: Invoices
    description: Create and manage invoices, proformas, and receipts
  - name: Products
    description: Manage your product and service catalog
  - name: Expenses
    description: Track and manage business expenses
  - name: Expense Categories
    description: Organize expenses with categories
  - name: Suppliers
    description: Manage expense suppliers and vendors
  - name: Settings
    description: API settings and configuration
  - name: Payments
    description: Payments received against invoices
  - name: Receipts
    description: Cash receipts (chitanțe) — standalone or paired with an invoice
  - name: Company Lookup
    description: Romanian company lookup (ANAF / VIES)
  - name: Invoice Series
    description: Manage invoice numbering series
  - name: Bank Accounts
    description: Manage IBAN bank accounts
  - name: E-Factura
    description: Romanian e-invoicing status and configuration
  - name: Supplier Bills
    description: Supplier invoices imported from the ANAF SPV inbox
  - name: VAT Rates
    description: Firm-scoped custom VAT rates on top of the Romanian catalog
  - name: Currencies
    description: Currencies enabled for the firm's bill templates
  - name: Languages
    description: Languages enabled for the firm's bill templates
  - name: Conta
    description: |
      Public ANAF data for the firm's CUI: fiscal profile (TVA scope, RTVAI,
      split TVA, status, e-Factura registration, CAEN) and annual balance
      sheets (cifra de afaceri, profit, capitaluri, datorii, salariați).

      Powered by the public ANAF webservices (no OAuth required for these
      endpoints). The data is cached locally and refreshed on demand via
      the `/sync` actions.
paths:
  /clients:
    get:
      tags:
        - Clients
      summary: List all clients
      description: Retrieves a paginated list of clients for your firm
      operationId: listClients
      parameters:
        - name: page
          in: query
          schema:
            type: integer
            minimum: 1
            default: 1
          description: Page number (1-indexed)
        - name: per_page
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
          description: Number of items per page
        - name: search
          in: query
          schema:
            type: string
          description: Search term for name, email, or CUI
        - name: client_type
          in: query
          schema:
            type: string
            enum:
              - b2b
              - b2c
          description: Filter by client type (`b2b` = companies, `b2c` = individuals)
        - name: sort
          in: query
          schema:
            type: string
            enum:
              - name
              - created_at
              - total_invoiced
              - invoices_count
          description: |
            Sort field. When omitted, results are ordered by aggregated
            `total_invoiced` DESC (the default surface for the client
            list).
        - name: order
          in: query
          schema:
            type: string
            enum:
              - asc
              - desc
            default: asc
          description: Sort order (ignored when `sort` is omitted)
      responses:
        '200':
          description: |
            List of clients. Each item includes a `metadata` block with
            `invoices_count` and `total_invoiced` aggregated across the
            firm's fiscal invoices (snapshot-aware), so the list view can
            render totals without a follow-up call.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    $ref: '#/components/schemas/ClientList'
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
components:
  schemas:
    ClientList:
      type: object
      allOf:
        - $ref: '#/components/schemas/PaginationMeta'
        - type: object
          properties:
            data:
              type: array
              items:
                $ref: '#/components/schemas/Client'
    ResponseMeta:
      type: object
      properties:
        version:
          type: string
          default: v1
        request_id:
          type: string
          format: uuid
          description: Unique request identifier for debugging
        response_time:
          type: string
          example: 23.45ms
    PaginationMeta:
      type: object
      properties:
        object:
          type: string
          default: list
        has_more:
          type: boolean
        total:
          type: integer
        page:
          type: integer
        per_page:
          type: integer
        total_pages:
          type: integer
    Client:
      type: object
      required:
        - id
        - object
        - name
      properties:
        id:
          type: string
          description: Unique identifier (CzUid)
          example: cli_1a2b3c4d5e
        object:
          type: string
          default: client
        name:
          type: string
          description: Client name
        email:
          type: string
          format: email
          nullable: true
        phone:
          type: string
          nullable: true
        cui:
          type: string
          description: Tax identification number (CIF/CUI)
          nullable: true
        cui_prefix:
          type: string
          description: Country prefix for CUI (e.g., RO)
          nullable: true
        rc:
          type: string
          description: Trade register number
          nullable: true
        client_type:
          type: string
          enum:
            - b2b
            - b2c
          description: '`b2b` for companies, `b2c` for individuals'
        address:
          type: string
          nullable: true
        city:
          type: string
          nullable: true
        county:
          type: string
          nullable: true
        country:
          type: string
          nullable: true
        postal_code:
          type: string
          nullable: true
        iban:
          type: string
          nullable: true
        bank:
          type: string
          nullable: true
        contact_person:
          type: string
          nullable: true
        created_at:
          type: integer
          description: Unix timestamp
        updated_at:
          type: integer
          nullable: true
          description: Unix timestamp (currently always null)
        metadata:
          type: object
          description: >
            Aggregated counters. Shape depends on the endpoint:

            - **List** (`GET /clients`): `{ invoices_count, total_invoiced }` —
            pre-computed
              via the `with_totals` join so every list item has the numbers needed for the
              dashboard view.
            - **Detail / create / update** (`GET /clients/{id}`, `POST`, `PUT`):
              `{ invoices_count, unpaid_total }` — computed per request against snapshots.
          properties:
            invoices_count:
              type: integer
            total_invoiced:
              type: number
              description: Sum of fiscal invoices issued to this client (list view only).
            unpaid_total:
              type: number
              description: Remaining unpaid balance (detail view only).
        stats:
          type: object
          description: >-
            Present only on detailed responses (`GET /clients/{id}`, `POST`,
            `PUT`).
          properties:
            total_invoiced:
              type: number
            total_collected:
              type: number
            avg_payment_days:
              type: integer
              nullable: true
              description: >-
                Average days between issue and payment on paid invoices. `null`
                if no paid invoices.
            last_payment:
              type: object
              nullable: true
              properties:
                date:
                  type: integer
                  nullable: true
                  description: Unix timestamp
                amount:
                  type: number
                currency:
                  type: string
                  nullable: true
                bill_id:
                  type: string
                  nullable: true
                  description: Invoice CzUid
                bill_number:
                  type: string
                  nullable: true
            monthly_series:
              type: array
              description: Last 6 months of invoiced vs. collected amounts, oldest first.
              items:
                type: object
                properties:
                  label:
                    type: string
                    example: Mar 2026
                  year:
                    type: integer
                  month:
                    type: integer
                  invoiced:
                    type: number
                  collected:
                    type: number
    ErrorResponse:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          default: false
        error:
          type: object
          required:
            - message
            - type
            - code
          properties:
            message:
              type: string
              description: Human-readable error message
            type:
              type: string
              enum:
                - api_error
                - authentication_error
                - invalid_request_error
                - rate_limit_error
                - permission_error
                - validation_error
            code:
              type: string
              description: Machine-readable error code
            param:
              type: string
              description: The parameter that caused the error
            doc_url:
              type: string
              format: uri
              description: URL to relevant documentation
        meta:
          $ref: '#/components/schemas/ResponseMeta'
  responses:
    UnauthorizedError:
      description: API key is missing or invalid
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Use your API key (sk_live_xxx or sk_test_xxx)

````