n-Acumatica Was Built API-First. That Still Doesn’t Build Your Integration For You.
Acumatica ships a REST API, plus an older SOAP-based contract API still in use on some long-running instances, covering financials, inventory, orders, and CRM data, documented and open from the start rather than bolted on as an afterthought. That openness genuinely makes custom integration more straightforward than with older, more closed ERPs, but someone still has to write the code that maps your fields correctly and keeps the connection running.
What you're actually working with
Acumatica's REST API is the current standard, with generic inquiry endpoints that let you query data off nearly any screen in the system, plus authentication through OAuth 2.0 bearer tokens. The older contract-based API, built on SOAP, still runs plenty of existing integrations that were built before REST became the default, and it's not automatically deprecated just because it's older.
Both expose business logic, not just raw tables, which matters: calling the API correctly triggers the same validations and workflows that happen when a person enters data through the screen, rather than writing directly to the database underneath.
Where custom work still starts
Acumatica's marketplace of prebuilt connectors is real and covers a lot of common ground. The moment you need a custom field exposed, a specific workflow triggered from outside the system, or a tool with no connector at all, that's development work against the REST API directly, not a settings toggle.
Businesses running an older contract-based SOAP integration sometimes come to us because it's grown brittle, breaking on version upgrades or timing out under load that's grown past what it was built for. Rebuilding that connection against the modern REST API usually holds up better going forward.
What We Build on Top of Acumatica's API
A custom field or workflow surfaced through the API
When something a business tracks lives in a custom field or triggers through a custom workflow Acumatica's standard connectors don't know about, we build the direct API integration that reaches it correctly.
A brittle SOAP integration, rebuilt on Acumatica's REST API
If an older contract-based integration is breaking on upgrades or buckling under more volume than it was built for, we rebuild it against the modern REST API so it keeps working as the business grows.
Building against Acumatica's API and stuck on something specific?
Tell us what you're trying to read or write, and we'll scope whether it's a standard inquiry call or needs something more.
Got a custom Acumatica screen or workflow nothing standard can reach?
Tell us what it is and what system needs to see it, and we'll map it against Acumatica's REST API to see what's buildable. And if Acumatica's API isn't actually where your integration is stuck, that's fine too, we write this kind of custom integration work against plenty of other systems too.
Let's talk