Public interface specification for IRIS v2.1 — the AI orchestration platform built for high-stakes enterprise workflows. Describes the intake endpoint through which external systems submit procurement requests, contract approvals, and compliance workflows to IRIS for AI-assisted processing, human-in-the-loop review, and audit-ready execution.
Validate the spec locally:
npx @redocly/cli lint openapi.yamlPreview as interactive docs:
npx @redocly/cli preview-docs openapi.yamlOr import directly into Postman, Insomnia, or any OpenAPI-compatible client.
openapi.yaml— the workflow intake contract: submission structure, document types, compliance flags, status tracking, and error responses.
This spec covers the intake boundary only. It does not describe IRIS's internal routing engine, LLM-assisted document extraction, approval chain configuration, or audit pipeline.
- 8 workflow types — procurement, contract approval, vendor registration, variation order, progress claim, CAPEX request, leave approval, compliance review
- Malaysian public sector context — ePerolehan reference field, Bumiputera participation flag, local content declaration, MYR-default currency
- PDPA-aligned — explicit consent flag per submission, sensitive data access control flag
- Multi-channel — JSON/API, multipart portal upload, email gateway, ERP integration (SAP, Oracle, Dynamics365)
- Webhook callbacks — optional status push as workflow progresses through stages
- Idempotent — safe to retry with
X-Idempotency-Key
IRIS is deployable on-premise, in private cloud (AWS/Azure/GCP Malaysian regions), or hybrid. No mandatory SaaS dependency. Data residency is fully configurable — no data leaves the configured boundary.