What this is
The Stowe Error Handling API is the single place every integrated system at Stowe Family Law reports to. Whenever one of our apps or integrations runs, it tells this service what happened: an error (something went wrong) or a success (the run completed). That gives us one source of truth for the health of every integration, one place to look when something misbehaves, and one engine that decides who needs to be told about a problem, and how.
Apps reporting in include Stowe Insights, Stowe Review Automation, the Stowe Client Portal (BIF, Form E and friends), Toca.AI, Salesforce and Nebulaw integrations, Prolink transactions, Navan, HiBob, Certinia and Asperato, plus anything new we build.
The idea in one flow
| 1. Log | An app calls POST /api/v1/events with what happened
and instantly gets an acknowledgement with an event id, proof the report landed. |
|---|---|
| 2. Classify | Errors are either technical (bad gateways, failed connections, retryable faults, for IT) or business (malformed data, missing fields, needs a human decision). |
| 3. Route | The alert engine matches each error against admin rules and personal subscriptions, then notifies the right people, without ever slowing down the app that reported it. |
| 4. Resolve | Errors carry a status (open, in progress, resolved, ignored) worked in the admin area or over the API, so nothing falls through the cracks and fix times are measurable. |
What you get
- For developers: a small, boring, reliable REST API. One endpoint to log, a couple to query and update. Full spec in the Swagger reference.
- For everyone at Stowe: an admin area with a live dashboard, searchable event browser, reports with charts and CSV export, and personal email subscriptions: pick the apps and severities you care about, instantly or as a daily digest, and watch individual errors for updates.
New here? Integrating an app: read
Getting started. Using the dashboard: jump to
Using the admin area.
Next: Getting started