Automatic Bank Adjustment Entry Using Rest API

Tracing REST API calls in Epicor Kinetic
While working on automating Bank Adjustment Entry in Epicor Kinetic, I explored how the UI communicates with the backend.
:light_bulb: Using Browser Developer Tools (Chrome/Edge → F12 → Network tab), I was able to trace the exact REST API calls made by the Kinetic UI:
:magnifying_glass_tilted_right: Steps:
:one: Open the Bank Adjustment Entry screen in Kinetic.
:two: Press F12 → Network tab → Filter by XHR/Fetch.
:three: Perform actions in the UI (New Group, Add Transaction, Save).
:four: Watch REST API calls such as:
/api/v2/odata/EPIC06/Erp.BO.BankAdjEntrySvc/GetNewBankGrp
/api/v2/odata/EPIC06/Erp.BO.BankAdjEntrySvc/Update
/api/v2/odata/EPIC06/Erp.BO.BankAdjEntrySvc/GetNewBankTran1
/api/v2/odata/EPIC06/Erp.BO.BankAdjEntrySvc/Update
:five: Inspect Headers (URL, Auth, API Key), Payload (JSON request body), and Response.
:link: With these steps, you can replicate API calls in Postman, curl for automation and integration.
:pushpin: Takeaway:
Epicor Kinetic UI is fully REST-driven. By tracing the network calls, we can discover exact request/response structures, which is invaluable for custom integrations and automation projects.
:raising_hands: This approach will also help interns, developers, and new Epicor users quickly understand how to work with Kinetic REST APIs.
hashtag#Epicor hashtag#Kinetic hashtag#RESTAPI hashtag#Integration hashtag#Automation hashtag#ERP