Skip to main content
GET

Authentication & Scope

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

Request

Response

200 OK returns an array of events, newest first. The endpoint currently returns the complete retained history without pagination.
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. 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.

Authorizations

Authorization
string
header
required

Personal Access Token

Path Parameters

form
number
required

The ID of the form.

integrationid
number
required

The ID of the integration.

Response

Successful

id
integer
read-only
date
string

Event date formatted as YYYY-MM-DD HH:mm.

status
enum<string>
Available options:
Success,
Error,
Skipped,
Processing,
Accepted,
Delivered,
Unknown
tracking_id
string | null
email_tracking
boolean
legacy_email
boolean
updated_at
string<date-time> | null
data
object | null

Submission ID, failure details, or email recipient outcomes.

can_retry
boolean

Whether this is the latest eligible failed attempt for an available completed submission.

retry_unavailable_reason
string | null

Why retry is unavailable; null when eligible.