Home
Home/Developers/Audit logs/Integrations/Auth0
Ed25519 signaturesSHA-256 hashes8 SDKs
Status
Sign inStart free
Home
Start here
Overview
Authentication
Errors
FAQ
API
Events
Canonical JSON and hashes
Documents
Anchoring a file
AI attestations
Attestation schema
Verifying attestations
Traces
Sealing a trace
Audit logs
Organizations
Streams
Portal
Public proof
Event schema
Exporting events
Integrations
Clerk
Auth0
Embeddable viewer
All endpoints
Reference
SDKs
Node.js
Python
Go
Java
Ruby
Rust
.NET
PHP
REST
Verification
Docs · Integrations

Auth0

Stream Auth0 tenant logs to Invoance and every sign-in, signup, password and email change becomes a signed audit event. The stream token is checked first.

Auth0 log stream docsAll integrations
sha-256 · 3a352297…2592
sha-256 · ba9bd2ac…5e6e
Set up
  1. Create the source

    In the dashboard open Audit Logs, then Integrations, and connect Auth0. Auth0 issues no secret, so set a token of 16 to 512 characters, or press Generate. Copy the URL and the token.

  2. Create a custom webhook stream

    In the Auth0 Dashboard open Monitoring, then Streams, then Create Stream, and choose Custom Webhook.

  3. Fill in the stream

    Payload URL: the webhook URL. Content Type: application/json. Content Format: JSON Array. Authorization Token: the token. Auth0 sends it on every delivery.

  4. Pick category filters

    Choose the stream's category filters. Only the codes in the map below become events; every other code is skipped.

Event map
Auth0 log codeAuth0 meaningBecomes
sSuccessful loginuser.signed_in
sloSuccessful logoutuser.signed_out
f, fp, fuFailed login: generic, wrong password, unknown useruser.sign_in_failed
ssSuccessful signupuser.created
sduUser deleteduser.deleted
scpSuccessful password changeuser.password_changed
sceSuccessful email changeuser.email_changed
limit_wc, limit_muIP blocked after repeated failed loginsaccount.blocked
  • f, fp, fu, limit_wc and limit_mu keep the exact code in metadata.auth0_code.
  • The actor is user_id with user_name as its name. ip and user_agent are stored as context.location and context.user_agent.
  • org_id and org_name on an entry route it to that organization, created if new. Entries without one follow the org-less policy.
  • du is not mapped: it coexists with sdu in Auth0's catalog and mapping both would double count. sdu is the record.
  • s fires on every successful login and f, fp and fu on every failed one. Filter the stream with your monthly quota in mind.
DeliveryResponse codes and skip reasons
AuthThe Authorization header must equal the token on the source, compared after trimming.
Success200 {"received": true, "accepted": n, "skipped": n}
Bad token401 invalid_authorization. Nothing in the batch is counted.
BatchA JSON array of {log_id, data} entries; a single object is accepted too. Up to 1 MB per delivery and 64 KB per entry.
RetriesEach entry is deduplicated by its log_id. One transient failure fails the whole batch with 500; Auth0 replays it and entries that already landed are not stored twice.
Timedata.date becomes occurred_at. Missing or invalid falls back to the receive time.

Proof infrastructure. Records are hashed, signed with your organization's Ed25519 key, and stored append-only, so anyone can check them later.

Products

  • Audit Logs
  • Event Ledger
  • AI Attestation
  • Document Anchoring
  • Traces

Developers

  • Documentation
  • API reference
  • SDKs
  • How it works
  • How traces seal
  • System status

Verify

  • Audit Log
  • Event
  • AI Attestation
  • Document
  • Trace

Company

  • Company overview
  • What is Invoance
  • Pricing
  • Security
  • Compliance teams
  • Finance teams
  • Partners
  • Brand assets
  • Resources
  • Help center
  • Contact
© 2025 – 2026 Invoance, Inc. All rights reserved.© 2026 Invoance, Inc. All rights reserved.
PrivacyLegal noticeLegal FAQ