Loading ForensicBlock
Preparing your blockchain forensics platform...
Preparing your blockchain forensics platform...
Modern firms run on case-management systems (NetDocuments, iManage, Litera) and internal automation. Firm-level API tokens let an authorized integration call our REST API on behalf of the org — without shipping a user's session. Tokens are hashed at rest; the plaintext is shown ONCE at creation.
Scope allowlist: * (full), read_only, watchlists, screening_records, reports, evidence, search. Mint a narrow integration token; don't hand over the keys to the kingdom.
SHA-256 hash stored; plaintext shown ONCE at creation with a copy-now warning. We never return the plaintext again.
DELETE is a soft-revoke (revoked_at + revoked_by stamped; preserves audit). Per-call usage logged with endpoint, method, status, IP, UA. Owner-only access.
Name + description + scopes + optional expiry. The dialog generates an fb_pk_<...> token.
Token displayed once. Copy to clipboard. The dialog warns: 'You will never see this again. Treat it like a password.'
Authorization: Bearer <token>. Calls to our API endpoints in the granted scopes.
Every call is usage-logged (endpoint, method, status). Owners review on the keys page.
Soft-revoke preserves the audit trail. Any integration using the token immediately fails.
Honesty rail
If a firm pastes a key into a Slack channel and we detect it (via a future secret-scan integration), we revoke automatically and email the owners. We hash; we never log the plaintext server-side either.
Book a demo and bring a closed matter (or a hypothetical one).