> ## 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. # List integration delivery logs > Returns a paginated list of integration delivery log entries for the authenticated project - which event was sent to which integration and whether it arrived. Use it to debug event delivery to third-party integrations. This is the delivery log, not a raw log of user events; the recorded events themselves are listed by `GET /v4/events`. Read-only. ## OpenAPI ````yaml /api-reference/rest-api-v4.yaml get /event-logs 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: Remote Configurations description: Server-driven configuration payloads and targeting delivered to the SDK - 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: Apple Ads description: Apple Ads reports, daily series, and connection status - name: Exports description: Asynchronous data exports - name: Events description: >- Subscription and purchase events recorded for the project, and the integration delivery log - 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: /event-logs: get: tags: - Events summary: List integration delivery logs description: >- Returns a paginated list of integration delivery log entries for the authenticated project - which event was sent to which integration and whether it arrived. Use it to debug event delivery to third-party integrations. This is the delivery log, not a raw log of user events; the recorded events themselves are listed by `GET /v4/events`. Read-only. operationId: v4ListEventLogs parameters: - name: limit in: query required: false schema: type: integer minimum: 1 maximum: 100 default: 20 description: Maximum number of log entries to return. - name: offset in: query required: false schema: type: integer minimum: 0 maximum: 100000 default: 0 description: Number of log entries to skip. - name: sort_by in: query required: false schema: type: string enum: - track_event_id - target_id - success - failed_code - updated_at - created_at default: created_at description: Field to sort by. - name: sort_order in: query required: false schema: type: string enum: - asc - desc default: desc description: Sort direction. - name: filter[track_event_id] in: query required: false schema: type: string description: Comma-separated track event IDs to filter by (max 50). - name: filter[target_id] in: query required: false schema: type: string description: >- Comma-separated target IDs to filter by (max 50). A target is an app in the project, not the integration the event was delivered to. - name: filter[success] in: query required: false schema: type: string enum: - 'true' - 'false' description: Filter by delivery outcome. Note the response field is `is_success`. - name: from in: query required: false schema: type: integer format: int64 minimum: 0 description: >- Start of the time range (Unix timestamp, seconds). The window between `from` and `to` can be at most 24 hours wide; a wider window is rejected with `400`. Omit both `from` and `to` to get the last 24 hours. Given alone, `to` defaults to the current time, so `from` alone works only for a point within the last 24 hours. To read further back, request consecutive 24-hour windows. example: 1776171456 - name: to in: query required: false schema: type: integer format: int64 minimum: 0 description: >- End of the time range (Unix timestamp, seconds). Given alone, `from` defaults to `to` minus 24 hours. With both ends set, `to` can be at most 24 hours after `from`. example: 1776257856 responses: '200': description: A list of integration delivery log entries. headers: Cache-Control: schema: type: string example: no-cache content: application/json: schema: type: object properties: object: type: string example: list url: type: string example: /v4/event-logs data: type: array items: $ref: '#/components/schemas/V4EventLog' has_more: type: boolean example: false total_count: type: integer description: Total number of matching log entries. example: 42 '400': description: >- Invalid request. Returned when `from` is greater than `to` (the error names the `from` field), or when the window between `from` and `to` is wider than 24 hours - including `from` alone set more than 24 hours in the past, since `to` then defaults to the current time. content: application/json: schema: $ref: '#/components/schemas/V4Error' '401': description: Unauthorized 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: V4EventLog: type: object description: >- One integration delivery attempt - a single event sent to a single integration. properties: object: type: string enum: - event_log track_event_id: type: string description: Track event ID - the event that was delivered. example: '98765' target_id: type: string description: >- ID of the target - the app in the project the event belongs to. It does not identify the integration; the delivery destination is the pair `integration_name` + `uid`. example: '456' is_success: type: boolean description: >- Whether the event was successfully delivered. The matching query filter is named `filter[success]`. example: true failed_code: type: string nullable: true description: Failure code if delivery failed; `null` on success. integration_name: type: string description: Name of the integration (for example, Amplitude or Mixpanel). example: Amplitude uid: type: string description: >- UID of the integration the event was delivered to. Together with `integration_name` it identifies the delivery destination. example: int-uid-123 created_at: type: string format: date-time description: When the log entry was created (ISO 8601 UTC). example: '2026-04-01T12:00:00Z' updated_at: type: string format: date-time description: When the log entry was last updated (ISO 8601 UTC). example: '2026-04-01T12:05:00Z' 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 reason: type: string description: >- Apple Ads query validation reason; unsupported_parameter for unknown/unsupported keys, invalid_parameter for malformed values or shapes. enum: - unsupported_parameter - invalid_parameter securitySchemes: secretAuth: type: http scheme: bearer bearerFormat: sk_… description: >- Bearer authentication using the project **Secret Key** (prefixed with `sk_`), used exactly as shown in the dashboard. Endpoints that support sandbox data take an explicit `environment` field or parameter. All v4 public endpoints require the Secret Key — see [Authentication](/reference/v4/authentication). Never expose the Secret Key in client-side code. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.