APIs and Integrations
Application Programming Interfaces (APIs) and Integrations represents the ability of applications or systems to hook into one or more components of a system we own - like the Kuali Financial System (KFS) General Ledger - to streamline the processesing of frequently-occuring, large-volume financial transactions. The scope and some examples of APIs and integrations our office currently manages include:
- E-Commerce (e.g., PayPal, Vantiv)
- Enterprise System Integration (e.g., HRMS Payroll to KFS)
- Collector Feed Integration (e.g., SIS Lockbox)
- Document API (e.g., Service Billing API)
- Subsidiary System API (e.g., Origami Risk)
All API and integration requests are subject to rigorous review of internal controls, IU accounting standards, and business process administration best practices. Submitting an API/integration request does not guarantee approval. If this request is not approved, our office may instead recommend more suitable solutions.
Our Support Role
The Office of the University Controller must approve any API or integration to the KFS General Ledger, and the review process for such requests includes first ensuring that the intended activity satisfies university compliance, controls, and reporting requirements.
Additionally, our team of business analysts and system administrators advise on the technical configurations and coordinate endpoint testing.
The request procedure for APIs and integrations is in final stages of development. Please check back for updates.