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

# Update integration status

> Enables or disables an integration.



## OpenAPI

````yaml /api-reference/rest-api-v4.yaml post /integrations/{integration_id}/status
openapi: 3.0.3
info:
  title: Qonversion REST API v4
  version: '4.0'
  description: >-
    Qonversion REST API v4 follows REST standards. It has predictable
    resource-oriented URLs, accepts JSON-encoded request bodies, returns
    JSON-encoded responses, and uses standard HTTP response codes,
    authentication, and verbs.
servers:
  - url: https://api.qonversion.io/v4
    description: Production
security:
  - secretAuth: []
tags:
  - name: Users
    description: Retrieve Qonversion users
  - name: User Properties
    description: Manage user-level attributes
  - name: Identities
    description: Link Qonversion users to your own auth IDs
  - name: Entitlements
    description: Entitlement definitions and user grants
  - name: Purchases
    description: A user's purchase history
  - name: Products
    description: Products configured in the Qonversion dashboard
  - name: Customers
    description: Aggregated customer records, properties, permissions, and metrics
  - name: Segments
    description: Dynamic and system segments of users
  - name: Experiments
    description: Paywall and offering A/B experiments
  - name: Screens
    description: No-code paywall screens — CRUD, publish, analytics
  - name: Analytics
    description: Charts, cards, cohorts, LTV, and insights
  - name: Exports
    description: Asynchronous data exports
  - name: Events
    description: Event catalog
  - name: Scheduled Reports
    description: Recurring reports delivered to external destinations
  - name: Integrations
    description: Third-party integrations configuration
  - name: Automations
    description: Event-driven automations
  - name: Project Settings
    description: Project-level configuration, secret, and store credentials
paths:
  /integrations/{integration_id}/status:
    post:
      tags:
        - Integrations
      summary: Update integration status
      description: Enables or disables an integration.
      operationId: v4UpdateIntegrationStatus
      parameters:
        - name: integration_id
          in: path
          required: true
          schema:
            type: string
            pattern: ^[a-zA-Z0-9._-]+$
            maxLength: 256
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/V4IntegrationStatusRequest'
      responses:
        '200':
          description: Integration status updated.
          headers:
            Cache-Control:
              schema:
                type: string
                example: no-cache
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Integration'
        '400':
          description: Invalid integration_id or request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '403':
          description: Feature not available
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '404':
          description: Integration not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '415':
          description: Unsupported media type
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '429':
          description: Rate limit exceeded
          headers:
            Retry-After:
              schema:
                type: integer
                example: 60
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '500':
          description: Internal error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '502':
          description: Storage error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
        '504':
          description: Upstream timeout
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/V4Error'
      security:
        - secretAuth: []
components:
  schemas:
    V4IntegrationStatusRequest:
      type: object
      required:
        - status
      properties:
        status:
          type: integer
          description: >
            Desired state. Only `0` (paused) and `1` (active) are accepted; `2`
            (error) is set exclusively

            by the delivery worker. To remove an integration, use `DELETE
            /v4/integrations/{integration_id}`.
          enum:
            - 0
            - 1
          example: 1
    V4Integration:
      type: object
      description: >-
        A single integration record. Credentials (API keys, webhook secrets) are
        configured out-of-band after creation and are not exposed in this shape.
      required:
        - object
        - id
        - url
        - title
        - integration
        - target_platform
        - active
        - created_at
        - updated_at
        - last_delivery_at
        - last_error_at
        - last_error_message
        - delivery_error_count
      properties:
        object:
          type: string
          example: integration
        id:
          type: string
          description: >-
            Integration identifier. Stable for the lifetime of the record
            (soft-deleted records keep their ID).
          example: gNl6hyM6
        url:
          type: string
          description: Canonical API path.
          example: /v4/integrations/gNl6hyM6
        title:
          type: string
          description: Caller-supplied display title.
          example: Amplitude — Production iOS
        integration:
          type: string
          description: >-
            Provider display title (not the lowercase slug used on create). Use
            for UI; for references in other requests use `id`.
          example: Amplitude
        target_platform:
          type: string
          description: Store the integration forwards events for. Case-sensitive.
          enum:
            - iOS
            - Android
            - Stripe
        active:
          type: integer
          description: >
            Integration state.

            - `0` — paused / draft (no events forwarded).

            - `1` — active (events forwarded).

            - `2` — error (delivery worker suspended the pipeline; inspect
            `last_error_message`/`last_error_at`). Cannot be set by callers.
          enum:
            - 0
            - 1
            - 2
        created_at:
          type: string
          format: date-time
          description: ISO 8601 creation timestamp.
          example: '2026-02-26T16:03:09Z'
        updated_at:
          type: string
          format: date-time
          description: ISO 8601 last-update timestamp.
          example: '2026-02-26T16:03:09Z'
        last_delivery_at:
          type: string
          format: date-time
          nullable: true
          description: >-
            ISO 8601 timestamp of the most recent successful delivery, or `null`
            if never delivered.
          example: '2026-04-22T10:12:33Z'
        last_error_at:
          type: string
          format: date-time
          nullable: true
          description: ISO 8601 timestamp of the most recent delivery failure, or `null`.
        last_error_message:
          type: string
          nullable: true
          description: >-
            Human-readable description of the most recent delivery failure, or
            `null`.
        delivery_error_count:
          type: integer
          description: >-
            Running count of delivery failures since the last successful
            delivery.
          minimum: 0
    V4Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - type
            - code
            - message
          properties:
            type:
              type: string
              enum:
                - request
                - resource
                - logical
                - internal
            code:
              type: string
              description: |
                Machine-readable snake_case error code. Examples include
                `invalid_data`, `invalid_request`, `invalid_product_id`,
                `not_found`, `already_exists`, `offering_already_exists`,
                `product_not_in_project`, `cannot_set_main_directly`,
                `cannot_demote_main`, `cannot_patch_experiment_variant`,
                `cannot_delete_experiment_variant`, and
                `cannot_setmain_experiment_variant`. Resource-specific codes
                are documented on the corresponding reference page.
            message:
              type: string
              description: Human-readable description. May change; do not parse.
            details:
              type: array
              nullable: true
              description: Per-field validation errors, present on 400 validation failures.
              items:
                type: object
                properties:
                  field:
                    type: string
                  message:
                    type: string
  securitySchemes:
    secretAuth:
      type: http
      scheme: bearer
      bearerFormat: sk_…
      description: >-
        Bearer authentication using the project **Secret Key** (prefixed with
        `sk_`, or `test_sk_` for sandbox). All v4 public endpoints require the
        Secret Key — see [Authentication](/reference/v4/authentication). Never
        expose the Secret Key in client-side code.

````