Compliance operations don't live in isolation. The moment a run closes, the evidence it produced needs to flow into your SIEM, your ERP, your CRM, or your custom risk dashboard. The people who care about that data are rarely in Cadenio — they're in Salesforce, ServiceNow, PowerBI, or an internal portal built by your engineering team. A public REST API is what makes Cadenio a first-class participant in your enterprise architecture instead of another silo that requires manual extraction.
Use case 1: sync run completions to your CRM or ERP. When a vendor onboarding run closes with committee approval, a webhook fires and your ERP creates the supplier record automatically. When a customer onboarding reaches go-live sign-off, Salesforce marks the opportunity as successfully onboarded and opens the expansion playbook. No manual data entry, no lag, no inconsistency between what Cadenio recorded and what your downstream system reflects.
Use case 2: trigger Cadenio runs from external events. Your ITSM raises a P1 incident ticket — a webhook hits the Cadenio API and launches the incident response flow immediately, with the ticket ID pre-populated and the on-call owner assigned. Your payroll system sends a new-hire event and Cadenio opens the employee onboarding run before the recruiter thinks to do it manually. External events become reliable flow triggers, not reminders that get missed.
Use case 3: build a live compliance dashboard from run data. Your risk team wants a real-time view of open SOC 2 controls, overdue SLA runs, and exception rates by business unit — across 14 process types. Rather than exporting CSVs, your engineering team queries the Runs API, filters by flow type and status, and feeds the data into a PowerBI workspace or a custom internal portal. The dashboard updates as runs close and new ones open, with no manual refresh cycle.
Use case 4: multi-system compliance automation. When a data retention run marks a disposal decision approved, the API call also updates the retention register in your data governance platform and archives the related records in your document management system. Three systems, one source of truth, one execution record. The compliance action and the downstream system updates are atomic from an audit perspective — because the audit trail is in Cadenio, and the API confirmation is attached to the run.
Use case 5: embedded workflow status in customer-facing portals. Enterprise customers who are part of your operational process — vendor portals, customer implementation trackers, partner compliance dashboards — can see the status of runs that involve them, without logging into Cadenio. Your engineering team builds the portal; the Cadenio API provides the run state, milestone completion, and open actions. Customers see progress without having full platform access. Partners see the compliance milestone their contract requires without needing a seat.
API access is an Enterprise feature because it creates a direct integration surface between Cadenio's execution layer and the rest of your stack. Scoped API keys mean integration teams get exactly the access the integration requires — runs:read for dashboards, runs:write for programmatic task updates, templates:read for sync jobs — and nothing more. Multiple keys per organization mean each integration has its own credential, with independent revocation and usage tracking.