Acumatica APIConnect Acumatica without building on its API
Acumatica has REST and SOAP APIs. Customers only: it is available on an Acumatica ERP instance, and API users, concurrent requests, and requests per minute are capped by the instance's license (a trial license allows 2 API users). If you're reading the docs because you need Acumatica to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Acumatica and your other tools.
- APIREST + SOAP
- AuthOAuth 2.0 / OpenID Connect
- AccessSelf-serve for customers
What the Acumatica API gives you
- Type
- REST + SOAP
- Authentication
- OAuth 2.0 / OpenID Connect (apps registered on the Connected Applications form) or cookie-based username/password sign-in
- Who can get access
- Customers only: it is available on an Acumatica ERP instance, and API users, concurrent requests, and requests per minute are capped by the instance's license (a trial license allows 2 API users).
- What it covers
- ERP entities exposed through contract-based endpoints, such as customers, vendors, sales orders, invoices, stock items, and financial documents.
- Limits
- API users, concurrent requests, and requests per minute are set per license (not published as fixed numbers), and requests are delayed once 50% of the per-minute limit is used and declined if the queue passes 20 requests or 10 minutes.
Official docs: help.acumatica.com. Checked September 2026. Vendors change access terms, so confirm with Acumatica before you build.
Building on the Acumatica API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Acumatica credentials, and manage tokens and refreshes. | Connect your Acumatica account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Acumatica task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Acumatica work off someone's desk, the build is the slow part.
What teams usually want the Acumatica API for
Entry posting
Caddi reads approved records and posts the entries into Acumatica automatically.
Reconciliation run
Caddi matches Acumatica records to source data and flags mismatches to the owner.
CRM to ERP sync
Caddi pushes Salesforce records into Acumatica on a daily run.
Acumatica API questions
Does Acumatica have an API?
Yes. Acumatica has REST and SOAP APIs, authenticated with OAuth 2.0 / OpenID Connect (apps registered on the Connected Applications form) or cookie-based username/password sign-in. The official documentation is at https://help.acumatica.com/.
How do I get access to the Acumatica API?
Customers only: it is available on an Acumatica ERP instance, and API users, concurrent requests, and requests per minute are capped by the instance's license (a trial license allows 2 API users).
Does the Acumatica API have rate limits?
API users, concurrent requests, and requests per minute are set per license (not published as fixed numbers), and requests are delayed once 50% of the per-minute limit is used and declined if the queue passes 20 requests or 10 minutes.
Can I connect Acumatica to my other tools without writing code against its API?
Yes. With Caddi you show the Acumatica task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Acumatica and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Acumatica with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Acumatica is reviewed before it runs in production, and every run is logged.
Connect Acumatica without the build.
Drop your work email and pick a time. We'll show you Caddi running your Acumatica workflow end to end.