Skip to main content
GET
Export Own Terms Events
Available in the Platform production API from October 22, 2026, including migration 119. Mobile distribution and genuine customer acceptance evidence remain separate from API availability.
Read presentation and acceptance events for the exact active EndUser in the authenticated project. Use a secret project key, a restricted key with end_users:read, or the same EndUser’s token. Device, upload and completion credentials are refused. This grants no organization-wide export access. Events are returned in ascending keyset order. limit is 1–100 and defaults to 100. When has_more is true, pass the returned opaque next_cursor unchanged to obtain the next page. Unknown query fields and malformed cursors are rejected. Responses use Cache-Control: no-store. Each event includes its version, content hash, server time, subject, project, channel and event_type (presented or accepted). A presentation event is not an acceptance. Events store no email, IP address, user agent or session token. For an audit packet, retrieve the immutable document for each event’s version and verify its hash. Do not describe today’s document as the wording accepted in an older event. Soft deletion refuses current receipt access while retaining prior event rows. Hard deletion of the subject or project cascades its events. This storage behavior does not establish an approved retention period or a complete account-deletion workflow.

Authorizations

Authorization
string
header
required

API key (sk_live_, sk_test_, rk_), device token (dtok_), or command-bound reset completion credential (rct_*; exact factory-reset ACK only)

Path Parameters

id
string
required

Query Parameters

limit
integer
Required range: 1 <= x <= 100
cursor
string

Response

Own event page

data
object[]
required
has_more
boolean
required
next_cursor
string | null
required