Skip to main content
A proof run is a window in your sandbox; finishing it returns the completeness, integrity and reconciliation report of that window. See Proof kit for how to run one and how to read the report.

Authentication

A sandbox API key (wede_test_), or a session of a user of your organisation. A production key receives 403 sandbox_key_required. Opening and finishing need reconciliation:manage; reading needs reconciliation:view. The wede team never has access.

Open a proof run

POST /v1/sandbox/proof-runs
string
required
1 to 120 characters.
201 Created
Only one run can be open at a time: another one returns 409 proof_run_open with proof_run_id, the id of the open run.

Finish a proof run

POST /v1/sandbox/proof-runs/{id}/finish
array
Optional. For devices that do not number their operations: up to 200 items of { "device": "...", "count": n }, where device is the device id or the identifier the device sends, and count how many operations it sent in the window.
200 OK returns the run with status: "finished", report_sha256, result and report. The window ends when you finish, and never more than 7 days after it opened. A finished run never changes; finishing it again returns 409 proof_run_finished. An excerpt of report:
string
pass when every exercised check passed, fail when one failed (named in failed), nothing_exercised when the window had nothing to measure.
object
offline_capture, out_of_order, duplicates, altered_message, completeness and own_records, each with exercised, passed (null when not exercised, and always for own_records) and detail.
string
SHA-256 of report in canonical JSON (object keys sorted at every level, no spaces). See The seal.

List and read

GET /v1/sandbox/proof-runs returns the last 50 runs of your organisation in data, without the report. GET /v1/sandbox/proof-runs/{id} returns one run with its report once finished.

Errors