Date: 2026-02-24 Status: Research complete — limited public documentation
| Data Object | REST API Read | REST API Write | Via SFTP/ETL | Via ERP Connector | Confidence |
|---|---|---|---|---|---|
| Invoices | Likely YES | Likely YES | YES | YES (SAP) | Medium — no public endpoint docs |
| Purchase Orders | Likely YES | Likely YES | YES | YES (SAP) | Medium |
| Suppliers | Likely YES | Likely YES | YES | YES (SAP) | Medium |
| Contracts | Likely YES | Likely YES | YES | YES (SAP) | Medium |
| Goods Receipts | Likely YES | Likely YES | YES | YES (SAP) | Medium |
| Purchase Requisitions | Likely YES | Likely YES | YES | YES (SAP) | Medium |
| Cost Centers / Accounts | Likely YES | Likely YES | YES | YES (SAP — accounting data) | Low-Medium |
| Materials / Items | Likely YES | Likely YES | YES | YES (SAP) | Medium |
| Approvals | Unknown | Unknown | N/A | N/A | Low |
| Payments | Unknown | Unknown | YES | Likely | Low |
Key finding: Ivalua has a REST API with 25+ endpoints and supports bidirectional data exchange, but API documentation is entirely behind authentication — no public developer portal, no public endpoint specs, no OpenAPI/Swagger, no Postman collection. Integration details are only available to customers and partners.
Ivalua's integration is built around three pillars, all built-in with no middleware required:
| Component | Purpose | Details |
|---|---|---|
| APIs (REST) | Push/pull data to/from external systems | REST web services, JSON/XML payloads |
| ETL | Flat file import, transformation, loading | Supports CSV, XML, Excel, text formats; scheduling; multiple format support |
| EAI | Orchestration of complex sequential integration flows | Manages multi-step integration actions including SFTP transfers |
| API Console | Developer tool for building and discovering APIs | Available within the platform |
| Integration Console | Monitoring and debugging | Raw request/response logging, payload downloads, re-trigger capability |
Critical gap: Unlike Coupa (which has compass.coupa.com with full endpoint documentation), Ivalua has:
All API documentation is available only to licensed customers and implementation partners.
Verdict: Write access almost certainly exists, but cannot be confirmed with public documentation.
Evidence for write capability:
Evidence that prevents full confirmation:
Confidence: Medium-High that write operations exist across major objects (invoices, POs, suppliers, contracts). The platform is clearly designed for bidirectional integration. But we cannot document specific endpoints.
No native connectors found on any major iPaaS platform.
| Platform | Status | Notes |
|---|---|---|
| Celigo | No connector | Not listed |
| Workato | No connector | Not listed |
| Zapier | No connector | Not listed |
| Make.com | No connector | Not listed |
| n8n | No connector | Not listed |
| MuleSoft | No connector found | Not in search results |
| Boomi | No connector found | Not in search results |
| Informatica | No connector found | Not in search results |
This is significant. The absence of iPaaS connectors means:
| Partner | Solution | Focus |
|---|---|---|
| Parasus | PIA (Packaged Interface Automation) | Ivalua ↔ SAP S/4 HANA integration |
| valantic | Certified SAP Connector | Ivalua ↔ SAP ECC / S/4 HANA |
| Cyrias | SAP integration services | Ivalua ↔ SAP consulting |
| APICONNECT | System integration for purchasing | Ivalua system integration |
Via Parasus PIA, the following data flows are confirmed:
Ivalua → SAP (write to SAP):
SAP → Ivalua (write to Ivalua):
This confirms that Ivalua accepts inbound data for: purchase requisitions, materials, services, goods receipts, purchasing groups, and accounting data.
Verdict: Likely YES, but no public endpoint documentation.
Evidence:
What we don't know:
/api/cost_centers or something else?)Confidence: Medium — the capability exists within the platform; whether it's exposed via REST API or only via ETL/flat file import is unclear.
Verdict: The platform has rich approval workflows, but programmatic API access is unconfirmed.
Evidence for approval workflow capability:
What we don't know:
/api/approvals/approve endpoint documented)Confidence: Low — approval workflows are sophisticated within the platform, but we have no evidence they're API-accessible from external systems.
Verdict: Likely possible via API or ETL, but no public documentation on specific status fields.
Evidence:
What we don't know:
Confidence: Low-Medium — status tracking is clearly a platform feature, but API-level access details are unavailable.
Verdict: Likely YES — the platform handles document attachments, but API upload details are unknown.
Evidence:
Confidence: Medium — document handling is core functionality; API-level upload mechanism is undocumented publicly.
| Orcha Need | Ivalua Capability | API Endpoint | Confidence |
|---|---|---|---|
| Push extracted invoice data | Platform supports invoice creation | Unknown endpoint | Medium — capability exists, no public API docs |
| Attach original PDF | Platform handles document attachments | Unknown endpoint | Medium |
| Write cost centers | Platform manages cost centers + CoA | Unknown endpoint | Medium — likely via ETL or API |
| Write account codes | Platform supports chart of accounts import | Unknown endpoint | Medium — likely via ETL |
| Trigger approval | Rich internal workflow engine | Unknown if API-accessible | Low — no evidence of external API for approvals |
| Manage approvers | Configurable approval chains | Unknown if API-accessible | Low |
| Read invoice status | Real-time status tracking exists | Unknown endpoint | Low-Medium |
| Read payment status | Payment tracking exists in platform | Unknown endpoint | Low |
| Receive status events | No webhook evidence | N/A | Low — likely polling only |
| Sync reference data | Bidirectional ERP sync confirmed | Unknown endpoint | Medium |
| Create CoA structure | CoA import supported | Unknown endpoint | Medium — likely via ETL |
| Approach | Cost | Complexity | Control | Best When |
|---|---|---|---|---|
| Direct REST API | Included with license | Medium-High | Full | Customer provides API docs + credentials |
| ETL / Flat File | Included | Medium | Medium | Batch operations, reference data sync |
| SFTP | Included | Medium | Medium | File-based invoice/PO exchange |
| Via ERP connector (PIA) | $$$+ (partner fee) | Low | Low | Customer already uses PIA/SAP |
Ivalua integration is feasible but requires customer engagement — unlike Coupa where we can build to publicly documented endpoints.
Approach:
Customer must provide API documentation. Ivalua's REST API exists with 25+ endpoints, but all docs are behind auth. The customer's Ivalua admin or implementation partner must share:
Fallback: ETL / flat file integration. If direct API access is complex or restricted, Ivalua's ETL toolset supports:
Consider the PIA partner path if the customer uses SAP. Parasus PIA provides packaged, bidirectional Ivalua ↔ SAP integration with confirmed data objects. Orcha could potentially plug into the SAP side if the customer already has PIA.
Key difference from Coupa: With Coupa, we can build a generic integration that works for any Coupa customer. With Ivalua, each integration will likely require customer-specific API documentation because Ivalua doesn't publish endpoint specs publicly.
What you'd need from an Ivalua customer: