Language-agnostic Sentinel ingest. Any runtime that can POST JSON over HTTPS can send crashes. Use cURL for a smoke test, then call the same endpoint from your main app’s global error path for live monitoring.
What is the Sentinel HTTP ingest API?
A single authenticated POST /api/v1/logs/ingest endpoint that accepts scrubbed crash JSON, runs built-in privacy scrubbing (<50ms design target), and queues async clustering/diagnosis. It never accepts a repository upload — 0 bytes durable source.
Stage
Timing
Built-in privacy scrub
<50ms design target (hot path)
Atlas / Athena / Aegis
Async after ACK (≥0.70 to surface fixes)
1. Endpoint & authentication
URL:POST https://lawde.net/api/v1/logs/ingest
Required header:x-lawde-api-key: $LAWDE_API_KEY
Also accepted:Authorization: Bearer $LAWDE_API_KEY
Content-Type:application/json
2. JSON payload contract
Field
Required
Notes
error_class
Yes
Exception name, e.g. TypeError
error_message
Yes
Human-readable message
stack_trace
Yes
Full stack string (scrubbed server-side)
file_path
Yes
Primary file for clustering signature
line_number
Yes
Positive integer
environment
No
Defaults to production
app_id
No
UUID of a workspace app
column_number
No
Non-negative integer
metadata
No
Object — may include lawdeignore_content
Repeats of the same crash join one issue. Look-alikes join when similarity is at least 0.85.
3. Phase A — cURL smoke test
Run once from your laptop or CI to confirm the key works. This is the same idea as test_ingest.sh in the Apps hub.