Skip to main content
GET
Tamper-evident export of your event log
Your desk’s event log, exportable and tamper-evident. Requires the orders:read scope. Cursor-paginated (limit default 100, max 500). Each export carries a chain_digest: events are hash-chained, so an auditor can verify offline that nothing was inserted, altered or dropped. Built for the compliance file, not just debugging.

Request example

Response example

Errors

Terms used here: order, statement, audit export, API key, scope, pagination. Full list in the terminology annexure.

Next steps

  • Statements, the billed view of the same activity.

Authorizations

X-ScripX-Key
string
header
required

Your API key, e.g. scripx_live_…. Bound to one firm; tenant isolation is enforced.

Query Parameters

limit
integer
default:100
Required range: x <= 500
cursor
string

opaque offset from a prior response's next_cursor

Response

OK

party_iec
string
period
string
count
integer
events
object[]
chain_digest
string

SHA-256 chain over the events as shown; recompute to verify integrity

algo
string