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

# List Provider Configurations

> Use this endpoint to retrieve a paginated list of provider configurations. You can filter results by status or provider ID.



## OpenAPI

````yaml /en/openapi/v3-current/flowker.yaml get /v1/provider-configurations
openapi: 3.1.0
info:
  description: >-
    Complete API reference for Flowker workflow orchestration services including
    catalog management, workflow definitions, executor configurations, provider
    configurations, and workflow executions.
  title: Flowker API
  version: 1.1.0
servers:
  - url: https://flowker.sandbox.lerian.net
security:
  - ApiKeyAuth: []
tags:
  - name: Health API
    description: Health and version endpoints for monitoring the Flowker service.
  - name: Catalog API
    description: >-
      Browse built-in providers, executors, and triggers available in the
      Flowker catalog.
  - name: Workflows API
    description: >-
      Create, update, activate, deactivate, clone, and delete workflow
      definitions.
  - name: Executions API
    description: Start workflow executions and track their status and results.
  - name: Executor Configurations API
    description: >-
      Configure, test, and manage external executor connections used by workflow
      nodes.
  - name: Provider Configurations API
    description: Configure, test, enable, and disable provider integrations.
  - name: Dashboard API
    description: >-
      Retrieve aggregated summaries of workflows and executions for operational
      dashboards.
  - name: Audit API
    description: Query and verify audit events for compliance and operational visibility.
  - name: Webhooks API
    description: >-
      Receive webhook callbacks from external systems to trigger workflow
      executions.
paths:
  /v1/provider-configurations:
    get:
      tags:
        - Provider Configurations API
      summary: List Provider Configurations
      description: >-
        Use this endpoint to retrieve a paginated list of provider
        configurations. You can filter results by status or provider ID.
      operationId: listProviderConfigurations
      parameters:
        - description: Filter results by status.
          in: query
          name: status
          schema:
            enum:
              - active
              - disabled
            type: string
        - description: Filter results by a specific provider ID.
          in: query
          name: providerId
          schema:
            type: string
        - description: >-
            Maximum number of items to return per page. Defaults to 10. Must be
            between 1 and 100.
          in: query
          name: limit
          schema:
            default: 10
            maximum: 100
            minimum: 1
            type: integer
        - description: >-
            Cursor for pagination. Use the value from the `nextCursor` field in
            a previous response to retrieve the next page.
          in: query
          name: cursor
          schema:
            type: string
        - description: Field to sort results by.
          in: query
          name: sortBy
          schema:
            default: createdAt
            enum:
              - createdAt
              - updatedAt
              - name
            type: string
        - description: Sort direction. Use `ASC` for ascending or `DESC` for descending.
          in: query
          name: sortOrder
          schema:
            default: DESC
            enum:
              - ASC
              - DESC
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProviderConfigurationListOutput'
          description: >-
            Indicates that the request was successful and the response contains
            the requested data.
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >-
            Indicates that the request was malformed or contained invalid
            parameters.
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >-
            Indicates an unexpected internal error. If this persists, please
            contact support.
components:
  schemas:
    ProviderConfigurationListOutput:
      example:
        items:
          - id: c3d4e5f6-a7b8-9012-cdef-345678901234
            name: ClearSale Production
            description: ClearSale anti-fraud for Pix transactions
            providerId: clearsale
            config:
              baseUrl: https://api.clearsale.com.br
            status: active
            createdAt: '2026-03-17T14:00:00Z'
            updatedAt: '2026-03-17T14:00:00Z'
        nextCursor: ''
        hasMore: false
      properties:
        hasMore:
          description: Indicates whether more pages are available.
          example: false
          type: boolean
        items:
          description: List of provider configurations in the current page.
          items:
            $ref: '#/components/schemas/ProviderConfigurationOutput'
          type: array
        nextCursor:
          description: Cursor for the next page.
          example: ''
          type: string
      type: object
    ErrorResponse:
      properties:
        code:
          description: Machine-readable error code with the FLK prefix.
          example: FLK-0001
          type: string
        message:
          description: Human-readable explanation of the error.
          example: Invalid input provided
          type: string
        title:
          description: Short error category title.
          example: Bad Request
          type: string
      required:
        - code
        - message
        - title
      type: object
    ProviderConfigurationOutput:
      example:
        id: c3d4e5f6-a7b8-9012-cdef-345678901234
        name: ClearSale Production
        description: ClearSale anti-fraud for Pix transactions
        providerId: clearsale
        config:
          baseUrl: https://api.clearsale.com.br
          environment: production
        status: active
        metadata:
          team: risk
        createdAt: '2026-03-17T14:00:00Z'
        updatedAt: '2026-03-17T14:00:00Z'
      properties:
        config:
          additionalProperties:
            type: object
          description: Provider-specific configuration.
          example:
            baseUrl: https://api.clearsale.com.br
            environment: production
          type: object
        createdAt:
          description: Timestamp when the configuration was created.
          example: '2026-03-17T14:00:00Z'
          format: date-time
          type: string
        description:
          description: Human-readable description.
          example: ClearSale anti-fraud for Pix transactions
          type: string
        id:
          description: Unique identifier of the configuration.
          example: c3d4e5f6-a7b8-9012-cdef-345678901234
          format: uuid
          type: string
        metadata:
          additionalProperties:
            type: object
          description: Custom metadata.
          example:
            environment: production
            team: risk
          type: object
        name:
          description: Name of the configuration.
          example: ClearSale Production
          type: string
        providerId:
          description: ID of the catalog provider.
          example: clearsale
          type: string
        status:
          description: 'Current status: `active` or `disabled`.'
          enum:
            - active
            - disabled
          example: active
          type: string
        updatedAt:
          description: Timestamp of the last update.
          example: '2026-03-17T14:00:00Z'
          format: date-time
          type: string
      type: object
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        API key for authenticating requests to the Flowker API. Provisioned via
        the API_KEY environment variable during deployment.

````