Skip to content

Beautiful Open-Source Form Builder

1.9 KB
Raw Blame
---
title: "List Integration Events"
description: "Review delivery attempts and retry eligibility for a form integration."
openapi: get /open/forms/{form}/integrations/{integrationid}/events
---

## Authentication & Scope

Use a Personal Access Token with `manage-integrations` and write access to the form's workspace.

## Request

<RequestExample>
```bash cURL
curl 'https://api.opnform.com/open/forms/123/integrations/42/events' \
  -H 'Authorization: Bearer YOUR_PAT'
```
</RequestExample>

## Response

`200 OK` returns an array of events, newest first. The endpoint currently returns the complete retained history without pagination.

<ResponseExample>
```json Success
[
  {
    "id": 1000,
    "date": "2026-10-03 14:00",
    "status": "Error",
    "tracking_id": null,
    "email_tracking": false,
    "legacy_email": false,
    "updated_at": "2026-10-03T14:00:00Z",
    "data": { "submission_id": 1234, "message": "Connection failed" },
    "can_retry": true,
    "retry_unavailable_reason": null
  }
]
```
</ResponseExample>

The `data` object contains the submission ID and any failure details. Tracked emails also include recipient outcomes. `Accepted` means that the mail transport accepted the email; delivery is not yet confirmed. `Skipped` means that no request was sent because integration conditions were not met.

Use `can_retry` to determine whether an event is eligible for [manual retry](/api-reference/integrations/retry-integration-event). When retry is unavailable, `retry_unavailable_reason` explains why. Only the latest eligible failed attempt for an available completed submission can be retried. The integration must be active.

## Error responses

- `401 Unauthorized`: authentication is missing or invalid.
- `403 Forbidden`: insufficient integration management permissions or workspace write access.
- `404 Not Found`: the form or integration does not exist in the requested scope.