---
title: "List apps"
method: GET
path: "/v3/openmeter/apps"
tags: ["OpenMeter Apps"]
---

# List apps

`GET /v3/openmeter/apps`

List installed apps.

## Query parameters

- `page` object
  - `size` integer — The number of items to include per page.
  - `number` integer — The page number.

## Response `200`

Page paginated response.

- AppPagePaginatedResponse — Page paginated response.
  - `data` BillingApp[], required
    - union — Installed application.
      - object — Stripe app.
        - `id` string, required — ULID (Universally Unique Lexicographically Sortable Identifier).
        - `name` string, required — Display name of the resource. Between 1 and 256 characters.
        - `description` string — Optional description of the resource. Maximum 1024 characters.
        - `labels` Labels — Labels store metadata of an entity that can be used for filtering an entity list or for searching across entity types. Keys must be of length 1-63 characters, and cannot start with "kong", "konnect", "mesh", "kic", or "_".
        - `created_at` string, date-time, required — An ISO-8601 timestamp representation of entity creation date.
        - `updated_at` string, date-time, required — An ISO-8601 timestamp representation of entity last update date.
        - `deleted_at` string, date-time — An ISO-8601 timestamp representation of entity deletion date.
        - `type` 'stripe', required — The app type.
        - `definition` object, required — The app catalog definition that this installed app is based on.
          - `type` 'sandbox' | 'stripe' | 'external_invoicing', required — Type of the app.
          - `name` string, required — Name of the app.
          - `description` string, required — Description of the app.
        - `status` 'ready' | 'unauthorized', required — Status of the app connection.
        - `account_id` string, required — The Stripe account ID associated with the connected Stripe account.
        - `livemode` boolean, required — Indicates whether the app is connected to a live Stripe account.
        - `masked_api_key` string, required — The masked Stripe API key that only exposes the first and last few characters.
      - object — Sandbox app can be used for testing billing features.
        - `id` string, required — ULID (Universally Unique Lexicographically Sortable Identifier).
        - `name` string, required — Display name of the resource. Between 1 and 256 characters.
        - `description` string — Optional description of the resource. Maximum 1024 characters.
        - `labels` Labels — Labels store metadata of an entity that can be used for filtering an entity list or for searching across entity types. Keys must be of length 1-63 characters, and cannot start with "kong", "konnect", "mesh", "kic", or "_".
        - `created_at` string, date-time, required — An ISO-8601 timestamp representation of entity creation date.
        - `updated_at` string, date-time, required — An ISO-8601 timestamp representation of entity last update date.
        - `deleted_at` string, date-time — An ISO-8601 timestamp representation of entity deletion date.
        - `type` 'sandbox', required — The app type.
        - `definition` object, required — The app catalog definition that this installed app is based on.
          - `type` 'sandbox' | 'stripe' | 'external_invoicing', required — Type of the app.
          - `name` string, required — Name of the app.
          - `description` string, required — Description of the app.
        - `status` 'ready' | 'unauthorized', required — Status of the app connection.
      - object — External Invoicing app enables integration with third-party invoicing or payment system. The app supports a bi-directional synchronization pattern where OpenMeter Billing manages the invoice lifecycle while the external system handles invoice presentation and payment collection. Integration workflow: 1. The billing system creates invoices and transitions them through lifecycle states (draft → issuing → issued) 2. The integration receives webhook notifications about invoice state changes 3. The integration calls back to provide external system IDs and metadata 4. The integration reports payment events back via the payment status API State synchronization is controlled by hooks that pause invoice progression until the external system confirms synchronization via API callbacks.
        - `id` string, required — ULID (Universally Unique Lexicographically Sortable Identifier).
        - `name` string, required — Display name of the resource. Between 1 and 256 characters.
        - `description` string — Optional description of the resource. Maximum 1024 characters.
        - `labels` Labels — Labels store metadata of an entity that can be used for filtering an entity list or for searching across entity types. Keys must be of length 1-63 characters, and cannot start with "kong", "konnect", "mesh", "kic", or "_".
        - `created_at` string, date-time, required — An ISO-8601 timestamp representation of entity creation date.
        - `updated_at` string, date-time, required — An ISO-8601 timestamp representation of entity last update date.
        - `deleted_at` string, date-time — An ISO-8601 timestamp representation of entity deletion date.
        - `type` 'external_invoicing', required — The app type.
        - `definition` object, required — The app catalog definition that this installed app is based on.
          - `type` 'sandbox' | 'stripe' | 'external_invoicing', required — Type of the app.
          - `name` string, required — Name of the app.
          - `description` string, required — Description of the app.
        - `status` 'ready' | 'unauthorized', required — Status of the app connection.
        - `enable_draft_sync_hook` boolean, required — Enable draft synchronization hook. When enabled, invoices will pause at the draft state and wait for the integration to call the draft synchronized endpoint before progressing to the issuing state. This allows the external system to validate and prepare the invoice data. When disabled, invoices automatically progress through the draft state based on the configured workflow timing.
        - `enable_issuing_sync_hook` boolean, required — Enable issuing synchronization hook. When enabled, invoices will pause at the issuing state and wait for the integration to call the issuing synchronized endpoint before progressing to the issued state. This ensures the external invoicing system has successfully created and finalized the invoice before it is marked as issued. When disabled, invoices automatically progress through the issuing state and are immediately marked as issued.
  - `meta` PaginatedMeta, required — returns the pagination information
    - `page` PageMeta, required — Contains pagination query parameters and the total number of objects returned.
      - `number` number, required
      - `size` number, required
      - `total` number, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden

---

[API](https://skmtc.net/kong/apis/konnect-api-go-sdk.md) · [All operations](https://skmtc.net/kong/apis/konnect-api-go-sdk/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kong/konnect-api-go-sdk/versions/f920f418f552/schema)