Developer docs
The API hashes what you send, signs it with your organization's Ed25519 key, appends it to a ledger, and verifies it on request.
| Base URL | https://api.invoance.com |
|---|---|
| Authorization | Bearer scheme and the key: Authorization: Bearer <key>. X-API-Key is read only when no Authorization header is sent. |
| Content-Type | application/json on every request with a body; other types are rejected before the handler runs. |
| Idempotency-Key | Optional on POST /v1/events, /v1/document/anchor and /v1/ai/attestations, required on POST /v1/audit/events. A retry with the same key gets the first response back for 24 hours. |
import { InvoanceClient } from "invoance";
// Reads INVOANCE_API_KEY from the environment.
const client = new InvoanceClient();
const result = await client.events.ingest({
eventType: "policy.approval",
payload: {
policy_id: "pol_8472",
approved_by: "risk_committee",
decision: "approved",
},
});
console.log(result.event_id);
Events
Append signed, hashed records of things that happened in your system, then verify them later.
4 endpointsDocuments
Anchor the SHA-256 hash of a file to a signed, append-only ledger record and check a file against it later.
5 endpointsAI Attestations
Signed records of what a model was asked, what it answered, and which model answered.
5 endpointsTraces
Group events, anchored documents and AI attestations into one sealed bundle with a composite hash.
8 endpointsAudit Logs
Append signed activity records for each of your end-customer orgs, then read, stream, export and verify them.
30 endpointsThe /v1/proof endpoints and GET /keys/{domain} take no API key. Anyone with a record id can read its public proof, or send a hash and get match_result and signature_valid back.