SigilbaseEvents API and SDKs, sealed on arrival.
Send records to Sigilbase through events API and SDKs: every delivery receipted, every gap declared, and evidence your auditor verifies offline without an account.
Available now.
- Status. Available now.
- Collected by. A receiver you point at.
- Connects with. An API key for the stream, created in the dashboard.
- Category. Receivers and the API.
What can be sent through Events API and SDKs
Each record becomes an event in the ledger, kept exactly as it arrived with a hash of those bytes beside it.
-
Event stream
Any event your own systems record, posted as JSON to the events API or through an SDK, with the actor, action, resource and payload you choose.
How it is collected
Your systems post events to the API, or through an SDK, under a key for the stream; each write is chained and sealed, and the response carries the sequence it took.
The evidence model
What every connector and receiver ships with, whatever the source:
- A receipt per collection: what was asked for, what arrived, the cursor before and after
- A declared gap for any interval nothing covers, never a blank
- A daily settlement once late records can no longer arrive
- The raw record, byte for byte, with its hash
- An evidence bundle anyone can verify offline
What you get
-
Sealed as it arrives
Every record is hashed and chained to the one before; every few minutes the chain is sealed into a signed checkpoint. A changed, deleted or reordered record fails verification at that exact point.
-
Continuity you can show
The receipts chain too, so an auditor sees not only the records but that nothing between them went uncollected, and where a gap was, that it was declared.
-
Verified without us
An export carries the open-source verifier. It runs offline, checks the chain, the receipts and the gaps, and needs no Sigilbase account. How the service is run.
Questions about Events API and SDKs
-
Does Sigilbase support Events API and SDKs?
Available now. Whatever arrives is written to a chained, signed ledger whose evidence anyone can verify offline with the open-source verifier, without a Sigilbase account.
-
What can be sent through Events API and SDKs?
Event stream: Any event your own systems record, posted as JSON to the events API or through an SDK, with the actor, action, resource and payload you choose.
-
How is Events API and SDKs evidence collected and verified?
Your systems post events to the API, or through an SDK, under a key for the stream; each write is chained and sealed, and the response carries the sequence it took. Every delivery is receipted: what was asked for, what arrived, and the cursor before and after. An interval nothing covers is declared as a gap, never left blank. Exports carry the standalone verifier, which checks the chain, the receipts and the gaps offline.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.