---
title: "Get configurations for the authenticated user or team"
method: GET
path: "/v1/integrations/configurations"
tags: ["integrations"]
---

# Get configurations for the authenticated user or team

`GET /v1/integrations/configurations`

Allows to retrieve all configurations for an authenticated integration. When the `project` view is used, configurations generated for the authorization flow will be filtered out of the results.

## Query parameters

- `view` 'account' | 'project', required
- `installationType` 'marketplace' | 'external' | 'provisioning'
- `integrationIdOrSlug` string — ID of the integration
- `teamId` string
- `slug` string

## Response `200`

The list of configurations for the authenticated user

- union
  - object[] — The list of configurations for the authenticated user
    - `completedAt` number — A timestamp that tells you when the configuration was installed successfully
    - `createdAt` number — A timestamp that tells you when the configuration was created
    - `id` string — The unique identifier of the configuration
    - `integrationId` string — The unique identifier of the app the configuration was created for
    - `ownerId` string — The user or team ID that owns the configuration
    - `status` 'error' | 'onboarding' | 'pending' | 'ready' | 'resumed' | 'suspended' | 'uninstalled' — The configuration status. Optional. If not defined, assume 'ready'.
    - `externalId` string — An external identifier defined by the integration vendor.
    - `projects` string[] — When a configuration is limited to access certain projects, this will contain each of the project ID it is allowed to access. If it is not defined, the configuration has full access.
    - `source` 'backoffice' | 'cli' | 'deploy-button' | 'external' | 'import-recommended-integrations' | 'marketplace' | 'oauth' | 'resource-claims' | 'v0' — Source defines where the configuration was installed from. It is used to analyze user engagement for integration installations in product metrics.
    - `slug` string — The slug of the integration the configuration is created for.
    - `teamId` string, nullable — When the configuration was created for a team, this will show the ID of the team.
    - `type` 'integration-configuration'
    - `updatedAt` number — A timestamp that tells you when the configuration was updated.
    - `userId` string — The ID of the user that created the configuration.
    - `scopes` string[] — The resources that are allowed to be accessed by the configuration.
    - `disabledAt` number — A timestamp that tells you when the configuration was disabled. Note: Configurations can be disabled when the associated user loses access to a team. They do not function during this time until the configuration is 'transferred', meaning the associated user is changed to one with access to the team.
    - `deletedAt` number, nullable — A timestamp that tells you when the configuration was deleted.
    - `deleteRequestedAt` number, nullable — A timestamp that tells you when the configuration deletion has been started for cases when the deletion needs to be settled/approved by partners, such as when marketplace invoices have been paid.
    - `customerDeleteRequestedAt` number, nullable — Record when the customer initited deletion, independent of whether `deleteRequestedAt` gets set.
    - `disabledReason` 'account-plan-downgrade' | 'disabled-by-admin' | 'disabled-by-owner' | 'feature-not-available' | 'original-owner-left-the-team' | 'original-owner-role-downgraded'
    - `installationType` 'external' | 'marketplace' — Defines the installation type. - 'external' integrations are installed via the existing integrations flow - 'marketplace' integrations are natively installed: - when accepting the TOS of a partner during the store creation process - if undefined, assume 'external'
  - object[]
    - `integration` object, required
      - `name` string, required
      - `icon` string, required
      - `isLegacy` false | true, required
      - `flags` string[]
      - `assignedBetaLabelAt` number
      - `tagIds` string[]
    - `completedAt` number — A timestamp that tells you when the configuration was installed successfully
    - `createdAt` number, required — A timestamp that tells you when the configuration was created
    - `id` string, required — The unique identifier of the configuration
    - `integrationId` string, required — The unique identifier of the app the configuration was created for
    - `ownerId` string, required — The user or team ID that owns the configuration
    - `status` 'error' | 'onboarding' | 'pending' | 'ready' | 'resumed' | 'suspended' | 'uninstalled' — The configuration status. Optional. If not defined, assume 'ready'.
    - `externalId` string — An external identifier defined by the integration vendor.
    - `projects` string[] — When a configuration is limited to access certain projects, this will contain each of the project ID it is allowed to access. If it is not defined, the configuration has full access.
    - `source` 'backoffice' | 'cli' | 'deploy-button' | 'external' | 'import-recommended-integrations' | 'marketplace' | 'oauth' | 'resource-claims' | 'v0' — Source defines where the configuration was installed from. It is used to analyze user engagement for integration installations in product metrics.
    - `slug` string, required — The slug of the integration the configuration is created for.
    - `teamId` string, nullable — When the configuration was created for a team, this will show the ID of the team.
    - `type` 'integration-configuration', required
    - `updatedAt` number, required — A timestamp that tells you when the configuration was updated.
    - `userId` string, required — The ID of the user that created the configuration.
    - `scopes` string[], required — The resources that are allowed to be accessed by the configuration.
    - `disabledAt` number — A timestamp that tells you when the configuration was disabled. Note: Configurations can be disabled when the associated user loses access to a team. They do not function during this time until the configuration is 'transferred', meaning the associated user is changed to one with access to the team.
    - `deletedAt` number, nullable — A timestamp that tells you when the configuration was deleted.
    - `deleteRequestedAt` number, nullable — A timestamp that tells you when the configuration deletion has been started for cases when the deletion needs to be settled/approved by partners, such as when marketplace invoices have been paid.
    - `customerDeleteRequestedAt` number, nullable — Record when the customer initited deletion, independent of whether `deleteRequestedAt` gets set.
    - `disabledReason` 'account-plan-downgrade' | 'disabled-by-admin' | 'disabled-by-owner' | 'feature-not-available' | 'original-owner-left-the-team' | 'original-owner-role-downgraded'
    - `installationType` 'external' | 'marketplace' — Defines the installation type. - 'external' integrations are installed via the existing integrations flow - 'marketplace' integrations are natively installed: - when accepting the TOS of a partner during the store creation process - if undefined, assume 'external'

## Other responses

- `400` — One of the provided values in the request query is invalid.
- `401` — The request is not authorized.
- `403` — You do not have permission to access this resource.
- `410`

---

[API](https://skmtc.net/vercel/apis/api.md) · [All operations](https://skmtc.net/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vercel/api/versions/61d1ba3f6dac/schema)