InvoanceInvoance
Log inStart free
Developers
Search docs…⌘K
Getting started
OverviewConceptsAuthenticationCreate an API key
API reference
EndpointsErrors
Audit Logs
Quick startIntegrationsEmbeddable viewerEvent schemaExporting eventsSDK reference
AI Attestations
Quick startAttestation schemaVerification & proofSDK reference
Events
OverviewSDK reference
Documents
OverviewSDK reference
Traces
OverviewSDK reference
SDKs
PythonNode.jsGoJavaRubyRust.NETPHPcURL
Verification
How it works
Support
API FAQ

Authentication

The Invoance API uses organization-scoped API keys to authenticate requests. Keys are hashed before storage, plaintext is never persisted after issuance.

API keys

All protected endpoints require a valid API key passed as a Bearer token. Keys are scoped to a single organization and grant access based on their assigned scope.

Authorization header
Authorization: Bearer invoance_live_XXXXXXXXXXXXXXXXXXXXXXXX

# Alternative header (both accepted, only one required)
X-API-Key: invoance_live_XXXXXXXXXXXXXXXXXXXXXXXX

Key format

invoance_live_XXXXXXXXXXXXXXXXXXXXXXXX
OpaqueKeys are randomly generated and contain no derivable information about the tenant or scope.
Hashed at restThe plaintext key is shown once at creation. Invoance stores only a secure hash, it cannot be recovered.
Non-transferableKeys are bound to a single organization. They cannot be used across tenants.
Immediately revocableRevoked keys are rejected on the next request with no propagation delay.

Scopes

Each API key is assigned one or more scopes at creation time. Requests using a key without the required scope are rejected with 403 Forbidden.

readRequired for all retrieval endpoints. Allows fetching ledger entries, attestations, and event records.
GET /document/:idGET /ai/attestations/:idGET /events/:id
writeRequired for all ingestion endpoints. Allows anchoring documents, creating attestations, and recording events.
POST /document/anchorPOST /ai/attestationsPOST /events

Enforcement

HTTPS onlyAll requests must be made over HTTPS. Plain HTTP is rejected immediately.
Org-scopedKeys are scoped to a single organization. Cross-tenant access is not possible.
Immediate revocationRevoked or inactive keys are rejected on the next request with no cache delay.
IP allowlistingOptional per-key IP allowlists can be configured from the dashboard.
Rate limitingAll API key requests are subject to per-plan rate limits. Exceeded limits return 429.

Unauthenticated endpoints

Public verification endpoints do not require an API key. These endpoints are read-only, rate-limited, and designed for independent third-party verification of anchored records.

# No authentication required
GET https://invoance.com/proof/event/{event_id}
GET https://invoance.com/proof/document/{event_id}
GET https://invoance.com/proof/ai/{attestation_id}
GET https://invoance.com/.well-known/invoance-platform-key

Related

Endpoints

Full API reference with request and response schemas.

Errors

HTTP status codes and error code reference.

01Audit logs02AI decisions03Documents04Business events05Whole workflows
Invoance

Neutral proof infrastructure for records that must survive scrutiny. Signed at creation. Verifiable outside your dashboard.

ALL SYSTEMS OPERATIONALEvidence infrastructure · Online

Build

  • Developer overview
  • API endpoints
  • Official SDKs
  • Authentication
  • Verification model

Use Invoance

  • Why Invoance
  • How it works
  • Compliance teams
  • Finance teams
  • Pricing

Verify

  • Audit log
  • AI attestation
  • Document
  • Ledger event
  • Sealed trace

Company

  • Resources
  • Security
  • Partners
  • Contact
  • System status
FIELD NOTES / 01Proof patterns for teams building trust.

Invoance provides cryptographic proof and verification infrastructure. It does not provide legal, financial, compliance, or regulatory advice.

Read proof disclaimer

Records anchored with Invoance are cryptographically signed and designed to reveal tampering. Invoance verifies that a specific record existed in a particular form at a particular time; it does not assess the record's accuracy, authenticity, legality, or underlying contents. Public verification links can be resolved without authentication. Invoance is not a custodian of funds, a legal authority, or a regulated financial institution. Using Invoance does not by itself satisfy any legal or regulatory requirement. Consult qualified legal or compliance professionals regarding your obligations.

© 2025 – 2026 Invoance, Inc. All rights reserved.
PrivacyLegalFAQ
PROOF, NOT PROMISES.