Dashboard
Work in the app
Upload guidelines, author question sets, run a case and review the decision — with no integration at all. A workspace admin invites the people who need it.
Open the dashboardDeveloper documentation
Underwriting, inside your own product
One HTTP API for the whole job. Create a case, attach its documents, run it against your rules, and read a decision with the evidence behind every answer.
curl -X POST \
https://api.underwriting.guru/v1/scenarios \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{ "name": "Q3 diligence" }'
# 201 → { "id": "0198c5f2-…", "status": "created" }Three ways in
Most teams use more than one. They share the same workspace, the same rules and the same audit trail.
API
Drive it from your own system
Everything the app does, over HTTP: create a case, attach documents, start a run, and read the decision with the evidence behind every answer.
Read the quickstartEmbed
Show a case inside your product
Put one case, read-only and themed to match, inside a page you serve. Your backend mints a short-lived handoff; nothing else crosses the boundary.
See how embedding worksGet an API key
Keys are minted in the dashboard, under Admin → Developers, by a workspace admin. A key looks like ug_live_…, carries only the scopes you give it, and is shown once — put it somewhere your servers can read and no browser can.
Integrating as a person rather than as a machine? A user token comes from your deployment's sign-in service over OAuth 2.0. Both credentials are covered in Authentication.
Where to next
QuickstartCredential to running underwrite, in four calls.AuthenticationUser tokens, API keys, scopes, and what each one may do.WebhooksBe told when a background task finishes, and verify it came from us.Embedding a caseThe allow list, the handoff, the SDK, theming and every failure mode.ConventionsPagination, errors, idempotency, rate limits, and the compatibility promise.API referenceEvery route, request and response, with a sample in your language.