Integrations

Integrations connect Qonversion to external marketing, analytics, attribution, and messaging platforms (Amplitude, Mixpanel, AppsFlyer, Adjust, Branch, Facebook, webhooks, etc.). An integration in v4 is the pipeline record — created with a display title and a target platform, then activated or paused. Per-provider credentials (API keys, webhook secrets) are configured out-of-band after creation; v4 does not expose credential fields.

Key concepts

Catalog — GET /v4/integrations/meta returns the list of supported provider slugs grouped by category, with the store platforms each slug supports.
Status — v4 reports the state as a status string: inactive, active, error or deleted. Only active and inactive are accepted as input on POST /status; error is set by Qonversion, not by you.
Lifecycle — Delete is soft: the record is flagged and stops forwarding events. The ID cannot be reused.

Supported integration slugs

Pass one of the following values as integration when calling POST /v4/integrations. The canonical list is whatever /v4/integrations/meta returns; this table is a point-in-time snapshot.

Category	Slugs
Analytics & marketing	`amplitude`, `appmetrica`, `facebook`, `firebase`, `mixpanel`, `posthog`, `segment`
Attribution	`searchads`, `adjust`, `appsflyer`, `branch`, `kochava`, `singular`, `split_metrics`, `asapty`, `tenjin`
Server	`amazon_s3`, `google_cloud_storage`, `slack`, `webhooks`
Email & push	`braze`, `clevertap`, `mailchimp`, `onesignal`, `pushwoosh`

Not every slug is available for every target_platform. /v4/integrations/meta reports allowedStores per slug.

`target_platform` values

The target platform is case-sensitive:

Value	Store
`iOS`	Apple App Store
`Android`	Google Play
`Stripe`	Stripe
`Paddle`	Paddle

`status` values

status is a string in every v4 response.

Value	Meaning	Who sets it
`inactive`	Paused / draft — no events forwarded.	Callers (create default, `POST /status`)
`active`	Active — events forwarded.	Callers (`POST /status`)
`error`	Delivery to this destination failed permanently. Set only on Amazon S3 and Google Cloud Storage integrations used as scheduled-report destinations, on the first delivery that fails with a non-retryable `4xx`. Event-forwarding integrations never enter this state.	Qonversion
`deleted`	The integration was deleted and no longer forwards events. A deleted integration may not appear in responses at all.	Callers, via `DELETE /v4/integrations/{integration_id}`

POST /status accepts active and inactive only — any other value, including error or a number, is rejected with a validation error. To recover a scheduled-report destination from error, fix its credentials and POST /status with {"status": "active"}.

Available endpoints

Method	Endpoint	Description
GET	`/v4/integrations`	List integrations (no pagination — returns the full project set)
POST	`/v4/integrations`	Create integration
GET	`/v4/integrations/meta`	Get supported-provider catalog
POST	`/v4/integrations/{integration_id}/status`	Pause (`inactive`) or activate (`active`) an integration
DELETE	`/v4/integrations/{integration_id}`	Delete integration (soft; ID cannot be reused)

Example: create an Amplitude pipeline for iOS

curl -X POST https://api.qonversion.io/v4/integrations \
  -H "Authorization: Bearer $QONVERSION_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Amplitude — Production iOS",
    "integration": "amplitude",
    "target_platform": "iOS"
  }'

Response (201 Created):

{
  "object": "integration",
  "id": "gNl6hyM6",
  "url": "/v4/integrations/gNl6hyM6",
  "title": "Amplitude — Production iOS",
  "integration": "Amplitude",
  "target_platform": "iOS",
  "status": "inactive",
  "created_at": "2026-02-26T16:03:09Z",
  "updated_at": "2026-02-26T16:03:09Z",
  "last_delivery_at": null,
  "last_error_at": null,
  "last_error_message": null,
  "delivery_error_count": 0
}

The integration field in responses carries the display title (e.g. Amplitude), not the lowercase slug you sent on create. Treat slugs as write-only identifiers; use id for references in other requests.

Example: activate then pause

# Activate
curl -X POST "https://api.qonversion.io/v4/integrations/gNl6hyM6/status" \
  -H "Authorization: Bearer $QONVERSION_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"status": "active"}'

# Pause
curl -X POST "https://api.qonversion.io/v4/integrations/gNl6hyM6/status" \
  -H "Authorization: Bearer $QONVERSION_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"status": "inactive"}'

Authentication

All v4 endpoints require a Secret Key. See Authentication.

Start here

Resource guides

REST API v4

Analytics API

Legacy: API v3

Key concepts

Supported integration slugs

`target_platform` values

`status` values

Available endpoints

Example: create an Amplitude pipeline for iOS

Example: activate then pause

Authentication

​Key concepts

​Supported integration slugs

​target_platform values

​status values

​Available endpoints

​Example: create an Amplitude pipeline for iOS

​Example: activate then pause

​Authentication

Key concepts

Supported integration slugs

`target_platform` values

`status` values

Available endpoints

Example: create an Amplitude pipeline for iOS

Example: activate then pause

Authentication