Luota reference
The navigable reference for the first monitor, Evidence Packet behavior, API calls, retry paths, and support-grade failure handling.
Start here
If you are wiring Luota for the first time, start with First monitor quickstart. It maps the whole path: choose one workflow, send one accepted signal, run one controlled failure, and leave with an Evidence Packet that another operator can trust.
Use the main integration docs when you want the full marketing quickstart and platform snippets. Use this reference when you need a stable implementation page you can search, link, and return to from errors.
What each page proves
- First monitor quickstart: the shortest path from empty workspace to a live signal.
- Evidence packets: what must be visible before Luota is credible as operational evidence.
- API reference: the ingest calls, token rules, limits, and response contract.
- API bad-day examples: invalid tokens, oversized payloads, rate limits, retries, and request ids.
Product rule
Frontend pages can promise clarity, but Luota should only ask for trust after the backend has accepted a real event and the product shows where that evidence will live.