Skip to main content

What you need from the portal

  • An API key with Create cases and Read cases (API keys).
  • The workflowId and, optionally, the version from the builder’s URL and toolbar.
  • A webhook config to receive the decision (Webhooks).

Submit a case

The response is 201 with { "caseId": "...", "requestId": "...", "status": "received" }. Repeating the same idempotencyKey returns the existing case with 200. The payload is validated against the Input node’s schema; the transaction subject needs method, a unique externalTransactionId and exactly one sender party.

Poll or wait for the webhook

GET /cases/{caseId} returns status (received, pending_review, decided) and result.decision. Prefer the webhook: case.pending_review arrives when the case reaches an analyst, case.decided when it is decided, case.decision_overridden if a manager corrects it.

Tags via API

POST /cases/{caseId}/tags with { "tag": "High Risk" } applies a tag from the managed vocabulary in Settings → Tags; anything else is rejected with 400. Needs the Manage tags scope.

Raise an information request via API

POST /cases/{caseId}/rfi with a templateId (or literal subject and body) and an rfiId idempotency key. One open request per case.

Full reference

Field-level documentation, error codes and the webhook payloads are in the Integration guide and the API reference.